W3C home > Mailing lists > Public > www-style@w3.org > April 2008

Re: [SelectorsAPI] Selector detection needed?

From: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Date: Mon, 07 Apr 2008 15:16:48 +0200
Message-ID: <47FA1EC0.6040506@disruptive-innovations.com>
To: www-style@w3.org

Anne van Kesteren wrote:

> There's no reason you couldn't do it on an empty document 
> (document.implementation.createDocument() iirc).

It's still an awful hack. Urgh, to say the least. It's like saying
|try { foo() } catch(e) { /* not implemented */ }| is better than
|if (typeof foo != "function") { /* same */ }|.

> It's also not clear 
> what advantage there is trying to feature detect first. As we know from 
> hasFeature() and all similar mechanisms, user agents lie because of 
> unknown bugs, because they need to get some page to work, et cetera.

s/cetera/cætera/ :-)

Anne, you really think we discover this _now_ ? I have always hated this
answer to this question because basically we decide not to implement
something because we feel implementors won't implement correctly...
That's called a free-hand. A license to kill if you prefer.

</Daniel>
Received on Monday, 7 April 2008 13:17:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:04 GMT