- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 12 May 2009 14:26:12 -0700
- To: Laurens Holst <laurens.nospam@grauw.nl>
- Cc: www-dom@w3.org, public-webapps <public-webapps@w3.org>
Note that you can already do document.createNSResolver(node) to get a resolver. But I agree that allowing nodes to be resolvers directly would have been the better way of doing it. / Jonas 2009/5/8 Laurens Holst <laurens.nospam@grauw.nl>: > Hi, > > Can I suggest adding the following to the XPathNSResolver > <http://www.w3.org/TR/DOM-Level-3-XPath/xpath.html#XPathNSResolver> > specification: > > “In a DOM implementation which supports the XPath 3.0 feature, as described > above, the |XPathNSResolver| interface will be implemented on the same > object which implements the |Node| interface.” > > This will allow nodes to be passed directly as XPath namespace resolvers. As > both XPathNSResolver and Node have an identical lookupNamespaceURI method, > this should be pretty trivial. > > Of course there is nothing preventing implementations from doing so already, > but it would be nice if this were standardised. > > Regards, > > ~Laurens > <http://www.w3.org/TR/DOM-Level-3-XPath/xpath.html#XPathNSResolver> > > -- > Note: New email address! Please update your address book. > > ~~ Ushiko-san! Kimi wa doushite, Ushiko-san nan da!! ~~ > Laurens Holst, student, university of Utrecht, the Netherlands > Website: www.grauw.nl. Backbase employee; www.backbase.com > >
Received on Tuesday, 12 May 2009 21:27:15 UTC