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

Re: [css3-selectors] Valid syntax that never represents an element

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 7 Jun 2012 15:59:12 -0700
Message-ID: <CAAWBYDBqqrO=Cm9nEJj+M_4Pm4x=dJw7QX1B_4FOfWiaXhwDwA@mail.gmail.com>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: www-style@w3.org
On Thu, Jun 7, 2012 at 3:48 PM, Simon Sapin <simon.sapin@kozea.fr> wrote:
> Le 07/06/2012 22:23, Tab Atkins Jr. a écrit :
>> The formal grammar is multiple kinds of broken.  It simply can't be
>> relied on.
>
>
> What should implementations rely on instead? (I’ve been using the grammar in
> selectors3 to work on cssselect’s parser recently, which was even more
> broken. Backslash-escapes simply weren’t there.)

Prose and guesswork.

>> It'll be fixed.
>
> Will it be fixed in Selectors level 3 or 4? How will this fix relate to the
> recent Syntax3 effort?
>
> Ideally I’d like to see everything defined in terms of the new Syntax3, but
> I understand that this stuff takes time and effort. Can any external help be
> useful?

I started working on Syntax again today.  It's coming. ^_^

~TJ
Received on Thursday, 7 June 2012 23:00:03 GMT

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