W3C home > Mailing lists > Public > www-style@w3.org > December 2007

Re: [CSS2.1] Parsing Selectors with Brackets

From: Gabriele Romanato <gabriele.romanato@gmail.com>
Date: Wed, 26 Dec 2007 09:31:25 +0100
Message-ID: <8aec6fbf0712260031t17f3b083hc31c0f703f8eb069@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>, www-style@w3.org
The problem lies in the correct error flagging.
that is, in the difference between a correct DELIM sequence and an incorrect
one.

{ }
{{}}

this is related to the single UA implementation, not to the specs. :-)

2007/12/26, fantasai <fantasai.lists@inkedblade.net>:
>
>
> Bjoern Hoehrmann wrote:
> > * fantasai wrote:
> >> While reviewing Gabriele Romanato's tests, I realized that we don't
> >> seem to specify matching brackets etc. when parsing selectors.
> >
> > This problem statement is too brief for me to follow you. Could you
> > elaborate? I note that the core grammar is quite clear that you can
> > not use { or } at all in selectors and (), [] only properly nested.
> > How is your problem different from e.g. using ";" or "<!--" "in a
> > selector"? There are many things about parsing style sheets and the
> > components of them left undefined, why would we need to address the
> > issue you are raising in CSS 2.1?
>
> The core grammar says what's correct. It doesn't say how to do error
> recovery. The question is, how is this parsed:
>
>   p { color: orange; }
>   p ( { color: red; } p { background: blue; } )
>
> Is the paragraph orange or blue?
>
> ~fantasai
> w
>
>


-- 
http://www.css-zibaldone.com/
http://mimicry.css-zibaldone.com/
Received on Wednesday, 26 December 2007 08:31:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:57 GMT