Re: hasFeature()

On Sun, Mar 9, 2014 at 5:39 PM, Philip J├Ągenstedt <> wrote:
> 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 Monday, 17 March 2014 15:13:46 UTC