- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Nov 2016 21:57:24 +0000
- To: public-svg-issues@w3.org
We talked about the issue on our call today. Since we've got 3 different implementers giving the OK for SVGUnitTypes to be an ordinary interface with no mixin, we're okay with that. @shepazu is going to look in to getting the W3C permissions sorted for @foolip in order to merge that pull request. We may need to temporarily add you to the GitHub SVG team, but I don't *think* that means you have to be formally assigned as a Google rep on the WG. If it gets too complicated, one of the WG members can make the edits. _____________________ For SVGZoomAndPan, we hope to get consensus from you all before making a change (if any). Things to consider (my personal opinion): - The attribute/behavior that these constants correspond to isn't implemented in any actively-developed user agent, and we've currently got it marked as "at risk" in the spec. - Even without seeing the data, I'm pretty sure that usage of the constants from the SVGSVGElement and SVGViewElement interfaces is just as low (meaning, essentially zero) as for the direct usage of the SVGZoomAndPan interface. As much as I'd love to see proper browser implementations of user zoom & pan control for graphics, I suspect that when that comes it will be via a new functionality that works for all web content, not just SVG, and that is compatible with existing pinch-zoom implementations. (And hopefully, it will be via a mechanism that doesn't "disable" zoom, it only defines which container isolates the zoom.) -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/291#issuecomment-261382561 using your GitHub account
Received on Thursday, 17 November 2016 21:57:30 UTC