[
https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s...
]
Thomas Amrhein commented on RF-11741:
-------------------------------------
Great. We still see the warnings in the log with RichFaces 4.3.4.
But as we will stay on RichFaces 4.3 for unknown time I will not be able to verify if the
new CSSParser fixes this issue.
Is there any upgrade of CSSParser planned for 4.3? For us it is not really required as
this is no critical issue in our project but we will appreciate it.
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: 5-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
For more information on JIRA, see:
http://www.atlassian.com/software/jira