- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 06 Jul 2019 16:51:00 +0000
- To: public-svg-issues@w3.org
I'd also like to hear more feedback & proposals from other implementation teams. If no one has plans to update their implementations to replace usage of SVGMatrix, etc. with DOMMatrix, then we really should be changing the spec to match reality. For reference, here are the tracking bugs for making the SVG* interfaces aliases to the DOM* equivalents: - [Chromium 709001](https://crbug.com/709001) - [Mozilla 1563444](https://bugzilla.mozilla.org/show_bug.cgi?id=1563444) - WebKit: [SVGMatrix](https://bugs.webkit.org/show_bug.cgi?id=191305), [SVGRect](https://bugs.webkit.org/show_bug.cgi?id=191377), [SVGPoint](https://bugs.webkit.org/show_bug.cgi?id=191376) If the final conclusion is that browsers do not want to update the DOM geometry interfaces to support attribute reflection, then we need to go through the [full SVG IDL](https://svgwg.org/svg2-draft/idl.html) and identify which uses of the geometry interfaces need a version with attribute reflection and which can still be replaced by the DOM equivalent. E.g., the value returned by `getCTM()` will never be associated with an attribute, so it could return a DOMMatrix without any changes to the DOMMatrix definitions. I'd also like any suggestions about how we could make the difference between a DOM* geometry interface and its SVG equivalent as transparent as possible to authors. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/706#issuecomment-508939654 using your GitHub account
Received on Saturday, 6 July 2019 16:51:02 UTC