- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 21 Aug 2013 17:35:47 -0700
- To: James Craig <jcraig@apple.com>
- Cc: "www-dom@w3.org" <www-dom@w3.org>, Indie UI <public-indie-ui@w3.org>
On Wed, Aug 21, 2013 at 5:03 PM, James Craig <jcraig@apple.com> wrote: > DOM WG (cc IndieUI WG), > > I recently noticed that DOM 4 effectively removed the functionality of DOMImplementation.hasFeature [1] > >> [hasFeature] should no longer be used, but continues to exist (and simply returns true) " > > > Remaining in the spec (presumably still intended to work) but without much detail listed are Node.isSupported [2] and Node.getFeature [3]. Given that these methods are so similar to the functionality of DOMImplementation.hasFeature(), is it okay to rely on these? > > As far as I can tell, there isn't a way to use standard object detection to allow authors to determine whether there is UA support for a particular type of event [4], so if these Node methods are no longer supported, please indicate the recommended way to allow feature detection of specific event types. No, use of these functions should be strongly discouraged. Assuming you follow best practice of providing on* properties on the event sources, that's an easy way to detect event types. ~TJ
Received on Thursday, 22 August 2013 00:36:38 UTC