Re: [svgwg] Decide what to do with zoom and pan (#56)

The SVG Working Group just discussed `Decide what to do with zoom and pan`, and agreed to the following:

* `RESOLUTION: remove zoomAndPan  attribute and expectation for zoom and pan feature.`

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: Decide what to do with zoom and pan<br>
&lt;krit> GitHub: https://github.com/w3c/svgwg/issues/56<br>
&lt;krit> AmeliaBR: zoom and pan is an attribute from SVG 1 that never got fully implemented by browsers<br>
&lt;krit> AmeliaBR: last implementation was the Adobe SVG Plugin<br>
&lt;krit> AmeliaBR: issue resurfaces last month when it was mentioned that there is interaction with other features<br>
&lt;krit> AmeliaBR: with some that are implemented on the DOM level and we got feedback from UAs what does and does not work<br>
&lt;krit> AmeliaBR: Blink does have some panning and zooming and it is buggy in the edge cases. Not sure if it counts as an implementation that needs preserving<br>
&lt;krit> AmeliaBR: unfortunately they don't have metrics<br>
&lt;krit> AmeliaBR: it works for standalone SVGs and embedded SVGs.<br>
&lt;krit> AmeliaBR: but it is not intecreted with zoomon<br>
&lt;krit> s/zoomon/zooming/<br>
&lt;krit> AmeliaBR: my proposal is to drop the attribtue<br>
&lt;krit> AmeliaBR: but keep the DOM properties but define them better in a way that interacts with other features like viewBox and the SVG view behaviour.<br>
&lt;krit> AmeliaBR: but it still needs work to figure out what the redefinition would look like<br>
&lt;krit> AmeliaBR: but that can be discussed separately<br>
&lt;krit> krit: what are the alternatives used today?<br>
&lt;krit> chris: manipulate the viewBox using script or apply transform using script<br>
&lt;krit> AmeliaBR: zoom and pan is about telling the browther to use its own zoom and pan with defaults and an attribute to disable that<br>
&lt;chris> it seems fine to me to drop the attr<br>
&lt;krit> AmeliaBR: since most browsers don't use zoom and pan features, ppl are not using the attribute to disable it. So if browsers would start implementing it it would break things to.<br>
&lt;krit> s/to/too/<br>
&lt;krit> myles: removing it makes sense to remove it<br>
&lt;krit> chris: Agree. It gives control over a not implemented feature.<br>
&lt;krit> AmeliaBR: I'd like to have an opt-in for a browser zoom and pan feature but it probably wouldn't work this way.<br>
&lt;krit> myles: If there is a new proposal we can have a clean cut<br>
&lt;krit> proposal: remove zoomAndPan  attribute and expectation for zoom and pan feature.<br>
&lt;krit> RESOLUTION: remove zoomAndPan  attribute and expectation for zoom and pan feature.<br>
&lt;krit> krit: 2nd part is the redefinition of the DOM features<br>
&lt;AmeliaBR> https://svgwg.org/svg2-draft/struct.html#__svg__SVGSVGElement__currentScale<br>
&lt;krit> AmeliaBR: there is a currentScale and currentRotate DOM properties on the SVGSVGelement<br>
&lt;krit> krit: for that we need to define in which cascade they apply?<br>
&lt;krit> AmeliaBR: yeah. They need to get redefined as something that is independent from the zoomAndPan attribute and how they interact with things like getCTM()<br>
&lt;krit> krit: Do we know in which order it applies to in combination with viewBox and transform attribute?<br>
&lt;krit> AmeliaBR: haven't looked into it.<br>
&lt;krit> krit: so there are more actions needed how the properties interact with other coordinate system manipulating attributes and functions like getCTM()<br>
&lt;krit> krit: should we open a new issue for that?<br>
&lt;krit> AmeliaBR: might make sense to have a new issue but we can leave it for now and I take an. action to start the edit and see how much work it is.<br>
&lt;krit> AmeliaBR: ok, so leave the issue open and AmeliaBR gets back to the group<br>
</details>


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

Received on Monday, 1 July 2019 20:23:24 UTC