[JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely
9:33 p.m.
ECSS parser is too aggressive when encountering non-standard CSS properties: selector
omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Fix For: 4.1.0.Final
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 p.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Karsten Wutzke updated RF-11741:
--------------------------------
Steps to Reproduce: Just use the respective rule in an ECSS file and add it to a page.
Add the CSS class to some container. You'll see the delivered ecss file is missing the
rule entirely. (was: Just use the above rule in an ECSS file and add it to a page. Add
the CSS class to some container. You'll see the delivered ecss file is missing the
rule entirely.)
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.1.0.Final
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 a.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11741:
-------------------------------
Fix Version/s: 4.2.0.Tracking
Thanks for reporting this issue - we'll see if we can address this in our upcoming dev
effort for 4.2.
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.2.0.Tracking
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-11741:
---------------------------------
We should look into upgrading CSS parser to new versions.
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.3-Tracking
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:54 a.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Thomas Amrhein commented on RF-11741:
-------------------------------------
This issue is very important for us. Google Chrome does not support many standard CSS
properties and designers have to use additional '-webkit-' CSS properties to
create good looking pages for Chrome.
Currently we run RichFaces 4.2.1. We launch our web page in the next months so I hope
there will be a fix for this in one of the next RF versions.
btw: I get a warning in the log which helped me to search for this Jira issue:
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource: Fehler
in Style-Regel. Ungültiger Token "-". Erwartet wurde einer von: <S>,
"}", ";", <IDENT>.
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource:
Ignoriere die folgenden Deklarationen in dieser Regel.
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.3-Tracking
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 a.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Thomas Amrhein edited comment on RF-11741 at 5/3/12 2:55 AM:
-------------------------------------------------------------
This issue is very important for us. Google Chrome does not support many standard CSS
properties and designers have to use additional 'webkit' CSS properties to create
good looking pages for Chrome.
Currently we run RichFaces 4.2.1. We launch our web page in the next months so I hope
there will be a fix for this in one of the next RF versions.
btw: I get a warning in the log which helped me to search for this Jira issue:
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource: Fehler
in Style-Regel. Ungültiger Token "-". Erwartet wurde einer von: <S>,
"}", ";", <IDENT>.
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource:
Ignoriere die folgenden Deklarationen in dieser Regel.
was (Author: tommy.a):
This issue is very important for us. Google Chrome does not support many standard CSS
properties and designers have to use additional '{noformat}-webkit-{noformat}' CSS
properties to create good looking pages for Chrome.
Currently we run RichFaces 4.2.1. We launch our web page in the next months so I hope
there will be a fix for this in one of the next RF versions.
btw: I get a warning in the log which helped me to search for this Jira issue:
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource: Fehler
in Style-Regel. Ungültiger Token "-". Erwartet wurde einer von: <S>,
"}", ";", <IDENT>.
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource:
Ignoriere die folgenden Deklarationen in dieser Regel.
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.3-Tracking
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:56 a.m.
[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Thomas Amrhein edited comment on RF-11741 at 5/3/12 2:54 AM:
-------------------------------------------------------------
This issue is very important for us. Google Chrome does not support many standard CSS
properties and designers have to use additional '{noformat}-webkit-{noformat}' CSS
properties to create good looking pages for Chrome.
Currently we run RichFaces 4.2.1. We launch our web page in the next months so I hope
there will be a fix for this in one of the next RF versions.
btw: I get a warning in the log which helped me to search for this Jira issue:
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource: Fehler
in Style-Regel. Ungültiger Token "-". Erwartet wurde einer von: <S>,
"}", ";", <IDENT>.
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource:
Ignoriere die folgenden Deklarationen in dieser Regel.
was (Author: tommy.a):
This issue is very important for us. Google Chrome does not support many standard CSS
properties and designers have to use additional '-webkit-' CSS properties to
create good looking pages for Chrome.
Currently we run RichFaces 4.2.1. We launch our web page in the next months so I hope
there will be a fix for this in one of the next RF versions.
btw: I get a warning in the log which helped me to search for this Jira issue:
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource: Fehler
in Style-Regel. Ungültiger Token "-". Erwartet wurde einer von: <S>,
"}", ";", <IDENT>.
03.05.2012 08:38:22 org.richfaces.resource.CompiledCSSResource$ErrorHandlerImpl
logException
WARNUNG: Problem parsing 'resJSFComponents/globalLayout/res.ecss' resource:
Ignoriere die folgenden Deklarationen in dieser Regel.
ECSS parser is too aggressive when encountering non-standard CSS
properties: selector omitted entirely
------------------------------------------------------------------------------------------------------
Key: RF-11741
URL: https://issues.jboss.org/browse/RF-11741
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: skinning
Affects Versions: 4.1.0.CR1
Reporter: Karsten Wutzke
Labels: ecss, parsing, skinning
Fix For: 4.3-Tracking
When defining rules like
{code}
.shadow
{
-webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
-moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}';
}
{code}
in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule
entirely and no shadows will be rendered. BTW it would be better to just omit the invalid
properties instead of the entire selector (box-shadow: ... alone works).
Most browsers don't support the box-shadow yet, so defining proprietary properties
*must* be possible. Note, this applies to a lot more properties than the above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4594
days inactive
4753
days old
richfaces-issues@lists.jboss.org
6 comments
5 participants
participants (5)
-
Brian Leathem (Updated) (JIRA) -
Karsten Wutzke (Created) (JIRA)
-
Karsten Wutzke (Updated) (JIRA)
-
Lukáš Fryč (JIRA)
-
Thomas Amrhein (JIRA)