myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeanne Waldman <>
Subject Re: [Trinidad] Adding additional accessibility features to skinning
Date Tue, 27 Nov 2007 21:54:54 GMT
I don't know off the top of my head, but you can test this with the 
@agent style.
If the base skin has @agent ie {.foo {some css properties}} and the 
extending skin has .foo not inside the @agent block, for ie, does this 
style get overridden?

It is probably the case that they do get overwritten, in which case, I 
see your point, but we don't do that same thing for the other @rules.
It makes the skin more complicated as well.

Matt Cooper wrote:
> Hi Jeanne,
> The any-* types are for users that do not require specific
> consideration.  It is useful because then someone could define some
> styles without worry of negatively impacting users with special needs.
>  In particular, it is most useful for people that extend skins.  If
> you are making a skin from scratch you can just use the defaults but
> if you don't want to override the painstakingly crafted styles for
> special needs users then any-* would give you this power.
> Is there another mechanism that exists today that would provide you this power?
> Thank you,
> Matt
> On Nov 19, 2007 3:58 PM, Jeanne Waldman <> wrote:
>> Hi Matt,
>> I don't understand how any-* works. It seems like this is the 'default'
>> which means there is no @accessibility-policy needed around the block of
>> css.
>> I don't understand your example of how this is useful. Can you elaborate?
>> Thanks,
>> - Jeanne
>> Matt Cooper wrote:
>>> I've logged an improvement request for the following issue:
>>> Before I start working on this, I wanted to gather feedback from you all.
>>> Thank you,
>>> Matt

View raw message