Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript (#291)

The SVG Working Group just discussed `Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript`, and agreed to the following:

* `RESOLUTION: Change SVGUnitTypes interface from NoInterface to an actual interface to match UA implementation behavior`

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript<br>
&lt;krit> GitHub: https://github.com/w3c/svgwg/issues/291<br>
&lt;AmeliaBR> s/AmeliaBR: ok/krit: ok/<br>
&lt;krit> AmeliaBR: This isn't really about zoom and pan but DOM enumerations.<br>
&lt;krit> AmeliaBR: But one example is for zoomAndPan which is no longer relevant with the last resolution<br>
&lt;krit> AmeliaBR: but the question still remains for SVGUniteTypes<br>
&lt;krit> s/SVGUniteTypes/SVGUnitTypes/<br>
&lt;krit> AmeliaBR: Should the interface that defines the constants should also be available as class that can be referenced. This would be consistent with other SVG DOM definitions.<br>
&lt;krit> myles: for implementations that do not implement zoomAndPan.. do they implement the DOM representation?<br>
&lt;krit> AmeliaBR: yes, they implement the DOM but not the functionality.<br>
&lt;krit> myles: how much JS is there that uses the APIs and what happens if we remove these properties<br>
&lt;AmeliaBR> https://chromestatus.com/metrics/feature/timeline/popularity/1102<br>
&lt;krit> AmeliaBR: 2 questions: Can we safely remove the properties and how much harm would it take.<br>
&lt;krit> AmeliaBR: there are use counters<br>
&lt;krit> myles: if we remove it those would turn to exceptions and the world breaks down<br>
&lt;krit> AmeliaBR: if the usage of the IDL property comes form enumerating on an element, there is no risk of deleting it<br>
&lt;krit> AmeliaBR: no idea why anyone would access the value of the attribute in any meaningful way since it has no functionality<br>
&lt;krit> myles: in other groups one UA is volunteering to go first. WebKit would likely not do it on this one. Can we ask Erik<br>
&lt;krit> Eric?<br>
&lt;myles> Willingers<br>
&lt;krit> krit: Try to involve him in the discussion. He is still around on github<br>
&lt;krit> AmeliaBR: I will followup with him.<br>
&lt;krit> ... back to this issue<br>
&lt;krit> krit: anything else than SVGUnitTypes and zoomAndPan?<br>
&lt;krit> AmeliaBR: I think SVGUnitTypes might be the only other one where the interface is not accessible (NoInterface object)<br>
&lt;AmeliaBR> https://www.w3.org/TR/2016/CR-SVG2-20160915/types.html#InterfaceSVGUnitTypes<br>
&lt;krit> AmeliaBR: this is userSpaceOnUse vs objetBoundingBox<br>
&lt;krit> AmeliaBR: currently the constants are the same across all of these... as defined in the spec, SVGUnitTypes isn't exposed. In Blink it is exposed.<br>
&lt;krit> AmeliaBR: have to check what all the other browsers do<br>
&lt;krit> AmeliaBR: SVGUnitTypes.&lt;constant> so it is its own interface.<br>
&lt;krit> AmeliaBR:  we should make the browsers match.<br>
&lt;krit> krit: do we know if it is in other browsers as well?<br>
&lt;krit> AmeliaBR: I know it is in Firefox, not sure about WebKit<br>
&lt;myles> interface SVGUnitTypes<br>
&lt;krit> AmeliaBR: so we get consistent browser behavior<br>
&lt;krit> AmeliaBR: it is also not implemented as a mixin<br>
&lt;krit> proposal: Change SVGUnit<br>
&lt;myles> https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/svg/SVGUnitTypes.idl<br>
&lt;krit> proposal: Change SVGUnitTypes interface from NoInterface to an actual interface to match UA implementation behavior<br>
&lt;krit> RESOLUTION: Change SVGUnitTypes interface from NoInterface to an actual interface to match UA implementation behavior<br>
&lt;myles> https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/svg/SVGZoomAndPan.idl<br>
&lt;myles> NoInterfaceObject<br>
&lt;krit> krit: so constant are not accessible for ZoomAndPan<br>
&lt;krit> krit: lets get back to SVGZoomAndPan after AmeliaBR talked to Eric<br>
&lt;AmeliaBR> github-got, end topic<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/291#issuecomment-507417361 using your GitHub account

Received on Monday, 1 July 2019 20:40:10 UTC