Re: [svgwg] Need to better define what rules apply to an element in an <svg:use> subtree.

The SVG Working Group just discussed `svg:use subtrees`.

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: svg:use subtrees<br>
&lt;krit> github:https://github.com/w3c/svgwg/issues/504<br>
&lt;krit> AmeliaBR: referencing element in another document and cloning in style rules of the other document (not only inline) is not what browsers implement<br>
&lt;krit> AmeliaBR: when you copy from another document only inline styles would be copied in.<br>
&lt;krit> krit: I am not sure if cloning styles from other documents to get cloned in into the current document is save.<br>
&lt;krit> AmeliaBR: why would it be an issue than anything else?<br>
&lt;krit> krit: it could load own resources<br>
&lt;krit> AmeliaBR: there are rules on loading further resources from loaded exrternal documents<br>
&lt;krit> AmeliaBR: stuff like line block from other files<br>
&lt;krit> AmeliaBR: that are not well defined<br>
&lt;krit> AmeliaBR: later to the issue I question even for the same document clone we do not have consistency with spec definition<br>
&lt;krit> AmeliaBR: clone is a known change from SVG 1.1 to be more consistent with web components but that might not me necessary anymore.<br>
&lt;krit> krit: why<br>
&lt;krit> AmeliaBR: because we closed the shadow dom and author scripts can't access the shadow DOM and this makes it more up to browsers how special internal things work<br>
&lt;krit> AmeliaBR: the other thing that changed: since 2016, web components have the idea of slotted elements sorted out now<br>
&lt;krit> AmeliaBR: elements that have their styles resolved in main document and included in current document is closer to SVG 1 styling cloning works.<br>
&lt;krit> AmeliaBR: this would get us back to the state of SVG 1.1 as far as same document style behaviour goes. Only browser not matching would be FF.<br>
&lt;krit> AmeliaBR: which never matched the spec<br>
&lt;krit> AmeliaBR: I have to talk to emilio if he could chnage the behavior of FF<br>
&lt;krit> AmeliaBR: under the SVG 1.1 you access all styles before you clone it. That assume processing in the external document but that is not what browsers implemented.<br>
&lt;krit> krit: do you think it would be an issue that we isolate styling for external use reference and just allow inline styling<br>
&lt;krit> AmeliaBR: I think browsers are consistent for inline styling<br>
&lt;krit> AmeliaBR: lets say you have a symbol element with an inner style element. Does this require cloning the style? I need to check what browsers do.<br>
&lt;krit> AmeliaBR: I want to be able to use CSS selectors to style "use" content<br>
&lt;krit> AmeliaBR: for external elements browsers usually don't pre-process the style other than they do for same document. So this needs to be tested.<br>
&lt;krit> krit: it sounds like you and Emilio would be the best persons to work on this. I will talk at TPAC with him when I see him.<br>
&lt;krit> AmeliaBR: I'll also try to ping Emilio and ask if FF could follow the other browsers and we get consistency<br>
&lt;krit> AmeliaBR: if you could ask browser implementers to look at this issue (especially web components) would be great.<br>
</details>


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

Received on Monday, 15 October 2018 20:19:45 UTC