- From: Simon Sapin <simon.sapin@exyr.org>
- Date: Mon, 30 Jun 2014 16:12:16 +0100
- 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())
http://dev.w3.org/csswg/css-syntax/#the-anb-type
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