W3C home > Mailing lists > Public > public-webapi@w3.org > February 2008

Re: [selectors-api] Selectors API comments: section 2

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 19 Feb 2008 12:58:26 +0100
To: "Jonas Sicking" <jonas@sicking.cc>, "Lachlan Hunt" <lachlan.hunt@lachy.id.au>
Cc: "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.t6rsvoud64w2qv@annevk-t60.oslo.opera.com>

On Tue, 19 Feb 2008 11:31:50 +0100, Jonas Sicking <jonas@sicking.cc> wrote:
> I do sort of think that it's a pity to disallow a selectors  
> implementation in a browser from implementing additional selectors on  
> top of the ones in the CSS implementation, for example for the reasons  
> Boris mentioned. I don't feel very strongly about it, but I'm wondering  
> what the rationale for forbidding it is.

So that the "API" stays consistent. If a new selector comes up that only  
makes sense in either we can always revisit this approach.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 19 February 2008 11:54:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 February 2008 11:54:29 GMT