[
http://issues.apache.org/jira/browse/ADFFACES-287?page=comments#action_12461303
]
Jeanne Waldman commented on ADFFACES-287:
-----------------------------------------
I could not reproduce this.
In purpleSkin.css, I had this definition (af|rocks is NOT in the base skin):
af|rocks {
border: 4px solid aqua;
-tr-inhibit: all;
}
And it generated:
.af_rocks {border: 4px solid aqua; }
I also tried flipping -tr-inhibit: all/border and it still worked.
Can you provide a more detailed example?
> Skin style inhibiting in non-inherited style blocks cause the entire block to
> be dropped when it should be a no-op
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ADFFACES-287
> URL: http://issues.apache.org/jira/browse/ADFFACES-287
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Components: Skinning
> Reporter: Matt Cooper
>
> If you have a skin style block where "-tr-inhibit: all;" is specified, it is
> supposed to drop all previous style definitions for that selector. This
> works great except if that selector wasn't defined in the skin you are
> extending.
> If a customer wants to implement their own skin (based on a default Trinidad
> skin), they should be able to add "-tr-inhibit: all;" definitions in all of
> their style blocks regardless of whether the selector for that style block is
> present in the Trinidad skin. Currently, if they do this any selectors not
> in the Trinidad skin will simply be ignored and any additional style
> definitions in that block will not make it into the generated CSS file.
> Inhibiting style definitions when none exist should be applying only to
> definitions from inherited skins, not the current skin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
