- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2016 08:32:22 +0000
- To: public-svg-issues@w3.org
Context: I was pointed here by @fsoder in https://codereview.chromium.org/2415413002/ Here's a test for whether `x implements SVGUnitTypes` is already supported: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/4581 Edge 14 and Firefox 51 have the constants everywhere. Chrome 55 and Safari 10 don't have them. A search for "SVG_UNIT_TYPE_" in httparchive:har.2016_09_15_chrome_requests_bodies finds [66 results](https://github.com/w3c/svgwg/files/535601/results-20161018-102112.csv.txt). 64 of them are from api-maps.yandex.ru and the other two are https://boxy-svg.com/api/frontend/modules.js and http://www.javascripture.com/javascripture.js. All of the are using the SVGUnitTypes object, and so don't depend on `x implements SVGUnitTypes`. @longsonr, given the lack of interop and seemingly low usage in the wild, would you be willing to drop `x implements SVGUnitTypes` from Gecko? To me it doesn't seem to add anything if `SVGUnitTypes` itself is exposed. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/svgwg/issues/291#issuecomment-254442089 using your GitHub account
Received on Tuesday, 18 October 2016 08:32:29 UTC