W3C home > Mailing lists > Public > www-svg@w3.org > January 2014

Re: hasFeature()

From: Stephen Chenney <schenney@chromium.org>
Date: Thu, 16 Jan 2014 16:41:56 -0500
Message-ID: <CAObCcUrTMbGeUqGtCVZ53X5kvPh_3i9xDy3U+8YF_+=J=r5z9A@mail.gmail.com>
To: Philip J├Ągenstedt <philipj@opera.com>
Cc: Anne van Kesteren <annevk@annevk.nl>, www-svg <www-svg@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
On Thu, Jan 16, 2014 at 11:10 AM, Philip J├Ągenstedt <philipj@opera.com>wrote:

> On Thu, Jan 16, 2014 at 6:39 PM, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> >
> > Hey,
> >
> > http://dom.spec.whatwg.org/#dom-domimplementation-hasfeature has a
> > weird lifeline basically for SVG and an open issue related to that
> > since it's not exactly clear what the details should be. Is SVG moving
> > away from the fantastical feature testing world as well? Should we
> > just simply always return true?
> If it would help, I could attempt to add use counters to Blink, get
> help determine how often hasFeature() is used, and how often it
> returns false.

Adding a UseCounter for hasFeature in Blink is non-trivial, but I am
getting a patch together for it.

In doing so, I noticed that SVGTests relies on the same code, so we will
also catch uses of the SVGTests requiredFeatures, requiredExtensions and
systemLanguage attributes.

Received on Thursday, 16 January 2014 21:42:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:50 UTC