- From: fantasai <fantasai@escape.com>
- Date: Mon, 16 Oct 2000 11:24:25 -0400
- To: www-style@w3.org
| Of course, as with my argument against :subject pseudo-thing, the :matches | pseudo-class is inherently more powerful than the !() syntax. | | For example: | | :not-matches(DIV.navbar > P# SPAN) > A | Now I'm confused about your syntax. It wouldn't be P:not-matches(DIV.navbar > # SPAN) > A ? | ..._would_ match the <A> in the fragment above, except if the <P> had a | SPAN descendant (which could be a sibling, child, or (nth level) niece of | the <A>.) This cannot, as far as I can tell, be described using !(). Quite true. | HOWEVER: At this point I should reiterate that in case this power scares | you, No, no. It's.. intriguing. The syntax scares me. | for CSS3 I am merely proposing that we allow the very simple | case: only at the end of a selector, and no '#' extended syntax. i.e., | make :matches be exactly equivalent to :subject but with a clear extension | path (since :subject cannot easily be extended).
Received on Monday, 16 October 2000 11:24:03 UTC