W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2014

Re: hasFeature()

From: Philip Jägenstedt <philipj@opera.com>
Date: Tue, 16 Sep 2014 20:30:59 +0200
Message-ID: <CAMQvoC=MwwFONH9fXnu9qZOjmAD3o8PPCP-G8N6caucwU_dxLQ@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, Stephen Chenney <schenney@chromium.org>, www-svg <www-svg@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
It's been on my todo list to send an Intent to Deprecate or something
for the change to make hasFeature() always return true, but it's not
high priority for me. If someone else wants to do it, go ahead.

Philip

On Tue, Sep 16, 2014 at 8:22 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Tue, Sep 16, 2014 at 11:11 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
>> On Tue, Sep 16, 2014 at 8:04 PM, Stephen Chenney <schenney@chromium.org> wrote:
>>> I took another look at the usage data now that it has been in Chrome for a
>>> while.
>>>
>>> hasFeature appears in just over 4% of page views (higher than the initial
>>> estimates) but it returns false only 0.0036% of the time.
>>>
>>> It seems to me that it is entirely safe to remove this from the spec and
>>> have it always return true during some deprecation period.
>>
>> https://dom.spec.whatwg.org/#dom-domimplementation-hasfeature still
>> requires that. Hopefully the change sticks this time and we can call
>> it a day :-)
>
> That's definitely within Blink's "acceptable to kill" range, so it
> seems likely to me that it'll be okay to just have it as a useless
> always-returning-true wart.
>
> ~TJ
Received on Tuesday, 16 September 2014 18:31:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:23 UTC