Previous Message
Next Message

Syntax of pseudo-elements/pseudo-classes

Sent by Cecil Ward on 9 April 2006 11:11


Philippe, thanks for the link to the SelectOracle tool. Your understanding
tallies with mine.

Francky, my point was that I have my suspicions about the W3C CSS validator,
and find the various CSS grammars unhelpful, particularly on points such as
the distribution of comments, distribution of whitespace, order of parsing
phases and escaping.

So I wanted a sanity check on this.

The SelectOracle tool, the W3C validator and my own brain agree that #1 is
invalid
	*\:first-line {}

So, "a colon may not be escaped". (If it is, it is seen as part of an
identifier, I suppose.)

Now the following nonsense
	*:first-line\:hover {}

ought to fail surely, but for a different reason. This is my interpretation
of it. The escaped colon makes the entire thing "first-line\:hover" into a
single identifier, as if the colon didn't exist in a sense. So what we get
is a long, unrecognised pseudo-class name.

Cecil Ward.

______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Previous Message
Next Message

Possibly related: