[Bug 25428] New: hasFeature removal was premature

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25428

            Bug ID: 25428
           Summary: hasFeature removal was premature
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected]

hasFeature was made to always return true on my request.

It looks like I underestimated just how much the use counter data can change
when it reaches the stable channel:
http://www.chromestatus.com/metrics/feature/timeline/popularity/230
http://www.chromestatus.com/metrics/feature/timeline/popularity/231

Removing hasFeature entirely is hopeless, and making it always return true is
also right above the highest threshold (0.06%) ever cited for Blink.

It would be very interesting to learn what the features that return false are,
but there's no way of collecting strings with the use counter system...

Sadly, I think the path of least resistance is to just go back to
special-casing SVG.

-- 
You are receiving this mail because:
You are on the CC list for the bug.