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