[richfaces-issues] [JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely

[Ronald Brill (JIRA)]

    [ https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966859#comment-12966859 ] 

Ronald Brill commented on RF-11741:
-----------------------------------

This should be fixed in CSSParser 0.9.14 (released yesterday). Please for the future, report your problems to the CSSParser project.

> 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 was sent by Atlassian JIRA
(v6.2.3#6260)