Re: hasFeature()
Philip Jägenstedt <[email protected]>
| Newsgroups | gmane.comp.web.svg,gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CAMQvoCk1zpdWrMVmKxbF__TocZN1+wDN8agGJLqktBk8OaaEkg@mail.gmail.com> |
On Fri, Jan 17, 2014 at 5:53 PM, Anne van Kesteren <[email protected]> wrote: > On Fri, Jan 17, 2014 at 11:45 AM, Philip Jägenstedt <[email protected]> wrote: >> There was some double work, which I apologize for, but these counters >> are now in Blink: >> https://code.google.com/p/chromium/issues/detail?id=335301 >> >> In a few months, we should be able to say both how common hasFeature >> itself is and how often it returns false. Hopefully we can make it >> always return true or even remove it altogether. > > Thanks Philip and Stephen. Please reply to this thread at that point > and I'll update the specification accordingly. 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. Philip