- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 19 Feb 2008 10:29:36 +0100
- To: "Jens Meiert" <jens.meiert@erde3.com>, "Boris Zbarsky" <bzbarsky@mit.edu>
- Cc: www-style@w3.org
On Tue, 19 Feb 2008 10:14:26 +0100, Jens Meiert <jens.meiert@erde3.com> wrote: > Referring to John's list: > > * E:empty – Chances are indeed that authors will use element selectors > instead, and I remember Eric raising other concerns concerning this > pseudo-class [1]. Element selectors? Eric's concerns are browser bugs and a slight misunderstanding of <img>. (I do agree it might make sense to have a pseudo-class that selects an element that either matches :empty or contains only whitespace text nodes. There's a Mozilla specific selector for that I believe.) > * E:lang(fr) – Probably the most questionable selector since apparently > replaceable by attribute selectors. Oh really? I don't think so. > * E:nth-of-type(n), E:nth-last-child(n), E:nth-last-of-type(n) – Trivial > objection: These selectors will bring much joy but will be rarely used > just because “cognitively too demanding”; I expect them to be used > absolutely nowhere in personal projects and quite rarely in complex > projects. That doesn't mean anything, it's just my two cents. I'd expect a few people to make examples on how you can put them to use and authors to follow by copy and pasting. http://files.myopera.com/dstorey/experiments/iTunesTable.html from http://dev.opera.com/articles/view/new-development-techniques-using-opera-k/ for instance. > [1] http://meyerweb.com/eric/thoughts/2007/08/17/running-on-empty/ -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Tuesday, 19 February 2008 09:25:40 UTC