Re: hasFeature()
Philip Jägenstedt <[email protected]>
| Newsgroups | gmane.comp.web.dom.general,gmane.comp.web.svg |
|---|---|
| Message-ID | <CAMQvoCkzNDDwMAezp25FNppVgCjjvbtTaaPmdsm5NZcc4GVf+g@mail.gmail.com> |
On Mon, Mar 17, 2014 at 10:13 PM, Anne van Kesteren <[email protected]> wrote: > On Sun, Mar 9, 2014 at 5:39 PM, Philip Jägenstedt <[email protected]> wrote: >> The counters have been in for a while now: >> >> http://www.chromestatus.com/metrics/feature/timeline/popularity/230 >> http://www.chromestatus.com/metrics/feature/timeline/popularity/231 >> >> These are not the numbers used to make decisions to deprecate or >> remove, but I think it gives a ballpark estimate of where it's going >> to end up. hasFeature itself is just above the 0.03% threshold for >> removal, and returning false is far below it. >> >> I suggest changing the spec to always return true now, and to track >> the other counter for a while longer before deciding. > > Done: https://github.com/whatwg/dom/commit/2e6526d447637de3b44813e90b15edadbcdcd10b Cool! For extra points I would also remove all the arguments, since extra arguments are ignored anyway. WebKit already treats the argument as optional and returns true for "document.implementation.hasFeature()" so it ought to be Web compatible. Philip