- From: Anne van Kesteren <annevk@opera.com>
- Date: Wed, 20 Aug 2008 11:20:50 +0200
- To: "Lachlan Hunt" <lachlan.hunt@lachy.id.au>, public-webapps@w3.org
On Tue, 19 Aug 2008 16:35:52 +0200, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote: > Lachlan Hunt wrote: >> I have now added a mandatory feature string. >> http://dev.w3.org/2006/webapi/selectors-api/#dom-feature > > It's been suggested to me that the spec should say something about > support for the other methods that use feature strings, including: > > interface DOMImplementationSource { > DOMImplementation getDOMImplementation(in DOMString features); > DOMImplementationList getDOMImplementationList(in DOMString features); > }; > interface DOMImplementation { > boolean hasFeature(in DOMString feature, > in DOMString version); > DOMObject getFeature(in DOMString feature, > in DOMString version); > }; > interface Node { > boolean isSupported(in DOMString feature, > in DOMString version); > DOMObject getFeature(in DOMString feature, > in DOMString version); > }; > > I'm not sure what exactly I should say about them, nor really understand > the purpose of them. But they're in DOM3Core and will need to be tested > in the test suite. Maybe just reference DOM Level 2 Core? There's a lot in DOM Level 3 Core that's not really implemented yet or necessarily desirable. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Wednesday, 20 August 2008 09:21:28 UTC