Re: [svgwg] Clarify that non-CSS rendering environments can override default width/height of embedded SVG (#762)

The SVG Working Group just discussed `Clarify that non-CSS rendering environments can override default width/height of embedded SVG`.

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: Clarify that non-CSS rendering environments can override default width/height of embedded SVG<br>
&lt;AmeliaBR> github: https://github.com/w3c/svgwg/issues/762<br>
&lt;AmeliaBR> krit: As I understand it, this is mostly about HTML canvas?<br>
&lt;AmeliaBR> Amelia: Yes. And it's more complicated than I originally thought when I created the issue. But we have a discrepancy between Firefox and Chromium. When drawing an SVG image to a canvas, Firefox uses viewBox and prefersAspectRatio. Chrome draws it at default sizes than uses bitmap scaling.<br>
&lt;AmeliaBR> krit: Do we have an example?<br>
&lt;AmeliaBR> Amelia: Not yet, unless it's in the linked browser bug.<br>
&lt;AmeliaBR> krit: So, we have different situations depending on what parameters go into the drawImage() function. Probably need some examples to consider them all.<br>
&lt;AmeliaBR> Amelia: Sounds good. I stand by my original concern about unintentional changes between SVG 1 and SVG 2, but the canvas issue is more complex.<br>
&lt;AmeliaBR> krit: Are there tests for that changed text in the spec?<br>
&lt;AmeliaBR> Amelia: Not sure how. It's about SVG embedding in non-CSS contexts.<br>
&lt;AmeliaBR> krit: Maybe we should then split it into two issues. One for the editorial changes, one specific to canvas.<br>
&lt;AmeliaBR> Amelia: Maybe wait until we have a clearer understanding of the canvas issue, then file it on HTML spec.<br>
&lt;AmeliaBR> krit: So, needs more tests.<br>
</details>


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

Received on Wednesday, 15 January 2020 20:49:23 UTC