Re: Supporting Scoped Selectors in Selectors API 2

On Sep 28, 2009, at 9:35 AM, Andrew Fedoniouk wrote:

> elm.querySelector(": div div, : div p");
> elm.querySelector(": > em, :> strong, :+code");
>
> Such construction definitely will not conflict with any future  
> selectors.

What makes you so sure? It seems to imply a pseudo-class, but not any  
particular pseudo-class, and maybe in the future there will be a more  
appropriate one to use with a naked colon at the beginning. Is there  
any problem (other than length), with being more specific, such as:

  elm.querySelector(":reference > em, :> strong, :reference +code");

> More strong (grammatically) alternative is "::" - double colons.

Also more confusing, as double colons are associated with pseudo- 
elements, not pseudo-classes.

Received on Monday, 28 September 2009 16:58:51 UTC