- From: <bugzilla@jessica.w3.org>
- Date: 2014年4月23日 13:52:59 +0000
- To: www-dom@w3.org
- Message-ID: <bug-25428-4009@http.www.w3.org/Bugs/Public/>
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: annevk@annevk.nl Reporter: philipj@opera.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org 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.
Received on Wednesday, 23 April 2014 13:53:01 UTC