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

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

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 07 Jun 2012 17:06:02 -0700
Message-ID: <4FD141EA.5040400@inkedblade.net>
To: www-style@w3.org
On 06/07/2012 03:48 PM, Simon Sapin 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.)
>
>> It'll be fixed.
>
> Will it be fixed in Selectors level 3 or 4? How will this fix relate to the recent Syntax3 effort?

If there's an error in Level 3, it should be fixed as an erratum.

> 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?

If you've got a patch for Selectors 3, I'll take it. ^_^

~fantasai
Received on Friday, 8 June 2012 00:06:48 GMT

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