Re: [svgwg] "Sizing properties" section should mention the "use" element (#607)

The SVG Working Group just discussed `"Sizing properties" section should mention the "use" element`, and agreed to the following:

* `RESOLUTION: For <use> elements in SVG 2.0, width and height have no effect as CSS properties.`
* `RESOLUTION: For nested <svg> (SVG without CSS layout box), using CSS properties to specify width and height will be marked at-risk.`

<details><summary>The full IRC log of that discussion</summary>
&lt;AmeliaBR> Topic: "Sizing properties" section should mention the "use" element<br>
&lt;AmeliaBR> Dirk: We deferred this last week, waiting for testing. Eric, were you able to do that?<br>
&lt;AmeliaBR> Eric: None of the properties currently use the width and height geo properties for either use or nested SVG. That may be a bug logically, but we have interop.<br>
&lt;AmeliaBR> Dirk: We also have sort-of interop in lack of support for image and foreignObject, no one supports except Blink.<br>
&lt;AmeliaBR> Eric: I didn't test that.<br>
&lt;AmeliaBR> Dirk: Can we resolve to exclude width and height as geometry properties on both use elements and nested SVG?<br>
&lt;AmeliaBR> Amelia: I don't like excluding nested SVG, since I think that is very confusing for authors.<br>
&lt;AmeliaBR> Dirk: Can we have a plan B, then? Can we mark them as At Risk in the spec.<br>
&lt;AmeliaBR> GitHub: https://github.com/w3c/svgwg/issues/607<br>
&lt;AmeliaBR> Amelia: Sounds good. Marking At Risk should also get more attention to the implementation issues.<br>
&lt;AmeliaBR> RESOLUTION: For &lt;use> elements in SVG 2.0, width and height have no effect as CSS properties.<br>
&lt;AmeliaBR> RESOLUTION: For nested &lt;svg> (SVG without CSS layout box), using CSS properties to specify width and height will be marked at-risk.<br>
&lt;AmeliaBR> Amelia: I can take the action on this. I have other edits to the &lt;use> section to work on. Hope to do it this week.<br>
</details>


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

Received on Monday, 17 December 2018 21:15:46 UTC