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

Re: [selectors-api] What DOM feature "Selectors API" belongs to?

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 14 Feb 2008 18:20:44 +0000 (UTC)
To: Sergey Ilinsky <castonet@yahoo.co.uk>
Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, public-webapi@w3.org
Message-ID: <Pine.LNX.4.62.0802141819260.20115@hixie.dreamhostps.com>

On Thu, 14 Feb 2008, Sergey Ilinsky wrote:
>
> And as for Safari. Yes, it does have document.querySelector, but! 
> because of some reason it doesn't have DocumentSelector/ElementSelector 
> objects exposed, it doesn't return StaticNodeList from 
> document.querySelectorAll, so, the question is - does it now support 
> "Selectors API"? Your answer is "yes". mine, according to your 
> specification - no.

Yet if the spec had had a hasFeature check, it would be returning "true" 
right now, since they would have implemented that too. So hasFeature() 
doesn't solve your problem either.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 14 February 2008 18:20:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 February 2008 18:20:57 GMT