- From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Date: Tue, 30 Oct 2012 11:42:22 +0100
- To: www-style <www-style@w3.org>
Hi, There is currently an open issue in Selectors API regarding the parsing of selectors. The current spec defines that the selectors use the selector grammar and should parse according to the rules in Selectors, but there are some known interoperability issues relating to things that currently not well defined. For example, the use of comments inside Selectors or unclosed functional pseudo-classes is not well defined and does not match implementation behaviour. This issue is more thoroughly described in this thread. http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0518.html I would like for Selectors 4 to more clearly address these issues by defining parsing in a better way. In particular, defining when an implementation should and should not throw a syntax error for those cases discussed in the thread. Additionally, I would like to move the definition for relative selectors and the related parsing to Selectors 4. This is a concept I defined in Selectors API Level 2, which basically allows selectors to begin with a combinator and have an implied :scope. http://dev.w3.org/2006/webapi/selectors-api2/#grammar -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Tuesday, 30 October 2012 10:42:49 UTC