Re: hasFeature()

On Fri, Jan 17, 2014 at 5:53 PM, Anne van Kesteren <> wrote:
> On Fri, Jan 17, 2014 at 11:45 AM, Philip Jägenstedt <> wrote:
>> There was some double work, which I apologize for, but these counters
>> are now in Blink:
>> 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:

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.


Received on Sunday, 9 March 2014 17:39:36 UTC