W3C home > Mailing lists > Public > www-style@w3.org > June 2014

Re: Selector parsing: It's easy to hit unexpected unicode-range tokens

From: Simon Sapin <simon.sapin@exyr.org>
Date: Mon, 30 Jun 2014 16:12:16 +0100
Message-ID: <53B17E50.6010306@exyr.org>
To: Boris Zbarsky <bzbarsky@MIT.EDU>, www-style list <www-style@w3.org>
On 30/06/14 15:34, Boris Zbarsky wrote:
> This came up in https://bugzilla.mozilla.org/show_bug.cgi?id=1032034
> Consider this rule:
>     #nav u+a { background: yellow; }

The person who reported the original bug also mentioned CSS minifiers 
that automatically remove whitespace, so this looks more common that I 
first thought.

> [...]
> It seems to me like either we should not have a separate unicode-range
> token and instead handle unicode ranges on the parser level or we should
> have some sort of special token reprocessing logic in the selector
> parser.  My preference is very much for the former.

I think we can do the former with a definition similar to this 
definition of <An+B> (the argument to :nth-child())


Itís ugly, but itís well-defined and it seems to be the "least worst" we 
can do here.

Simon Sapin
Received on Monday, 30 June 2014 15:12:43 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:41 UTC