W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: [selectors-api] Investigating NSResolver Alternatives

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 14 Jul 2008 22:07:03 +0200
To: "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <op.ueast1lp64w2qv@annevk-t60.oslo.opera.com>

On Mon, 14 Jul 2008 21:30:18 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> Anne van Kesteren wrote:
>>> How do I select all the inline SVG images on the page?
>>     div > svg, p > svg
>>  though it's not quite as thorough as your solution.
> Offhand, you're missing td, span, body to cover any sort of decent range  
> of images....  But yes, much less thorough, indeed.  And hard to get  
> "right".


>> On the other hand, this seems extremely complex to author and not  
>> something most authors would come up. :-)
> That's possible, but I would think that the authoring of the query would  
> be by one of the various toolkits, and the author would call  
> getSVGImages() or some such.


>> If this is the kind of scenario we're trying to get NSResolver defined  
>> for it does not be worth it.
> Last I checked, the main envisioned use of the querySelector* APIs was  
> to speed up existing queries toolkits do.  Might be worth asking them  
> what they think would be useful.


http://api.dojotoolkit.org/jsdoc/dojo/HEAD/dojo.query (It doesn't even do  
XML unless all names are lowercase.)


I agree that asking them explicitly would be good though, but it seems  
like so far the need was not compelling enough to implement it. (And  
libraries generally have gone to extreme lengths to implement other things  
not natively supported by browsers or not available cross browser.)

Anne van Kesteren
Received on Monday, 14 July 2008 20:08:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:11 UTC