Intent to Deprecate and Remove: Node.isSupported

[Philip Jägenstedt]

Primary eng (and PM) emails

phi...@opera.com

Summary

Remove this from the Node interface:

boolean isSupported([Default=Undefined] optional DOMString feature,

                    [TreatNullAs=NullString,Default=Undefined] optional DOMString version)

Motivation

This function was removed from the DOM Living Standard <http://dom.spec.whatwg.org>

It merely forwards to DOMImplementation.hasFeature, which is in turn spec'd as a hard-coded list of "features" to support.

This is old-school feature detection which doesn't work.

Usage information from UseCounter

This was on pdr's list <http://crbug.com/332191> of features which are "unused or have extremely low usage numbers". I don't have the exact numbers. This counter was in Chrome 31, so there's no need to wait any longer.

Compatibility Risk

Any scripts that call e.g. elm.isSupported(...) will throw an exception. Node that Firefox Nightly doesn't support this API, so it cannot be a big problem.

Row on feature dashboard?

No.

Requesting approval to remove too?

Yes, I'd like to remove the feature immediately with no deprecation period.

[Adam Barth]

LGTM.  Feature that have been removed from the spec and are never called seem like good candidates to remove.  :)

[Eric Seidel]

lgtm2.

[TAMURA, Kent]

LGTM3.

--
TAMURA Kent
Software Engineer, Google

[Jochen Eisinger]

lgtm3