[
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