W3C home > Mailing lists > Public > www-style@w3.org > March 2008

RE: [CSS21] [css3-selectors] attribute selectors

From: Alan Gresley <alan1@azzurum.com>
Date: Tue, 11 Mar 2008 18:48:41 -0700
To: fantasai <fantasai.lists@inkedblade.net>
cc: www-style@w3.org
Message-ID: <20080311184841.34b83c2f3c9bef00757a2c62c0fb7450.85ee944320.wbe@email.secureserver.net>

fantasai wrote:

> Finally, wrt the resolution in
>    http://lists.w3.org/Archives/Public/www-style/2008Feb/0331.html
> about making empty string substring match selectors invalid, I'll note that
> Firefox, Opera, and IE7 all treat [attr~=""] as valid but not matching anything
> and Safari matches it against some values of attr. Are we sure we want to make
> these invalid rather than specifying existing behavior?
> 
> ~fantasai


Please keep existing behavior. Just because these attributes with empty string may not have 'overtly obvious' use cases, why change the behavior when all UA are consistent in how the handle empty strings. [alt*=""] should be a match likewise since the majority of UA are consistent. Since I plan on heavily using attribute selectors to style my pages I do see empty substrings as valid and possibly very powerful. They are "not" meaningless and silly selectors.


I will provide this link again.

http://en.wikipedia.org/wiki/Thinking_outside_the_box


I have finished my template which is now live.

http://css-class.com/test/


I have eleven IDs or classes in the source. I know I could cut that back to five (which I will work towards). The rest of the style will come from the use of sibling and attribute selectors. I would like time to experiment and see if the attributes with empty substring do have use cases before they all disappear :-)


Alan

http://css-class.com/
Received on Wednesday, 12 March 2008 01:49:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:02 GMT