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

Re: [CSS2.1] escapes, characters and parsing

From: Peter Moulder <peter.moulder@monash.edu>
Date: Sun, 27 Mar 2011 11:09:01 +1100
To: www-style@w3.org
Message-id: <20110327000901.GA24968@bowman.infotech.monash.edu.au>
On Fri, Mar 25, 2011 at 07:59:07AM +0100, Bjoern Hoehrmann wrote:

> The ["\2a"] selectors would match elements with node name `*`.

That's what I would expect to happen, but if WebKit or any other UA
treats it as universal selector, then I can't say that the spec is
completely clear about it.

In the table at the start of section 5.1, the E[foo] etc. entries are
presumably to be interpreted as meaning “the token value after
processing escapes is E/foo”[*1], which would suggest that the ‘*’ in
the first line should also be interpreted as “the token value after
processing escapes”.

[*1]: Unless we interpret them as literally "E", "foo" etc. examples,
      in which case the meaning of the selector "p" wouldn't be defined.

Section 5.3 does say “written "*"”, but note that much the same direct
wording is also taken for things like rgb() syntax, which is allowed to
be written with escapes.  [At least, all UAs I've tested allow it to
use escapes, and that seems like the right thing given that the
FUNCTION token can use escapes.]

pjrm.
Received on Sunday, 27 March 2011 00:09:32 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:38 GMT