- From: Larry Israel <lisrael@cruzio.com>
- Date: Mon, 31 Mar 2003 13:43:18 -0800
- To: www-style@w3.org
>> How about :current ? > > http://www.w3.org/TR/1998/NOTE-CSS-potential-19981210#id16717669191 ? > > </Daniel> Thanks, Daniel. Sorry, I was not aware of that document (Note). Thanks for your efforts on that front, and thanks for bringing it to my attention. The Abstract for that Note says "This Note attempts to document all the features that have been suggested for CSS, and that are not part of CSS2.... Please, give feedback before the 5th of February 1999." Therefore, that document seems to have little bearing on CSS3. (I'm sure someone will correct me if I misunderstand the status of the document.) If I understand correctly, that Note contains a list of rejected features, essentially. Maybe some of them will be included in the future, but, so far, the working group has rejected them. I looked at http://www.w3.org/Style/CSS/current-work Selectors seemed the most-likely place for it http://www.w3.org/TR/css3-selectors/ But I don't see any similar feature and in this discussion, no one has said this is part of the CSS3 recommendation. I hope I'm not out of line by making one last argument about the issue. An a:current (or a:local, or a:here, if you prefer) pseudo class seems central to what the web is about and how the web is actually used. It would be easily understood by web authors and *very* widely used in menu bars. As an outsider to the W3C standards process, it's hard to understand why this feature is not part of the CSS3 recomendation. Is it be difficult for web clients to implement? Is there some other good reason? Meanwhile, the CSS3 recommendation (and much discussion here) includes features that, in comparison, seem far less important and much more difficult to use. How can :current reasonably be excluded from the same spec that includes nth-last-of-type? (to take just one esoteric example; hope you get my drift). Larry
Received on Monday, 31 March 2003 16:43:24 UTC