Re: [svgwg] how should display:contents affect SVG conditional processing attributes? (#579)

The SVG Working Group just discussed `how should display:contents affect SVG conditional processing attributes?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;myles> Topic: how should display:contents affect SVG conditional processing attributes?<br>
&lt;myles> GitHub: https://github.com/w3c/svgwg/issues/579<br>
&lt;myles> AmeliaBR: I haven't looked at this issue.<br>
&lt;myles> AmeliaBR: it shouldn't. The SVG attribute should happen first before any CSS, but...<br>
&lt;myles> krit: Let's open a new topic<br>
&lt;myles> s/krit: Let's open a new topic//<br>
&lt;myles> AmeliaBR: The processing attributes are all defined to happen even if something is display:none. They exist on their own level. I don't think we should try to complicate things by having it interact with display:contents.<br>
&lt;myles> krit: What about inline SVG? We have to define how svg contetns define display content<br>
&lt;myles> AmeliaBR: That's already defined at the basic level. If something is hidden because of conditional processing, then adding display:contents on it won't change anything. If it's displayed, then okay, it's displayed but now you're doing whatever we arleady defined display:contents to do on that element. The only thing that's not defined is if you put display:contents directly on a &lt;switch><br>
&lt;myles> krit: &lt;reads spec><br>
&lt;myles> krit: doesn't that mean that no matter which SVG we have in the document, it will always have display:none on the root and therefore not get displayed?<br>
&lt;myles> AmeliaBR: Yes, but i don't know how that affects conditional processing<br>
&lt;myles> AmeliaBR: SVG already defines, conditional processing says, of these 3 children, this is the one that gets displayed, but that child has display:none, then nothing gets display:none. So the same thing would happen if we're display:contents'ing that child. It's two separate sets of processing, and if the net result is nothing gets displayed, then nothing gets displayed.<br>
&lt;myles> krit: Sounds reasonable to me.<br>
&lt;myles> krit: Why not just take the next node or whatever?<br>
&lt;myles> krit: hrm.<br>
&lt;myles> AmeliaBR: Anything else would be adding a lot of complication for something that is hardly ever going to come up.<br>
&lt;myles> krit: Do we think there's anything on SVG's side that we need to resolve?<br>
&lt;myles> AmeliaBR: probably not. Possibly a clarification to the conditional processing bit where it says "not affected by display:none" we could chagne it to say "not affected by display:none or display:contents"<br>
&lt;myles> krit: Does that need to go into SVG or into CSS Display?<br>
&lt;myles> krit: We can follow up.<br>
&lt;myles> krit: Let's wait for the feedback that we get from heycam and fantasai<br>
&lt;myles> AmeliaBR: I found the relevant statement in SVG. "Note that the values of display have no effect on &lt;switch>" that's all-inclusive and we don't need to change anythign.<br>
&lt;AmeliaBR> "Note that the values of properties display and visibility have no effect on ‘switch’ element processing."<br>
&lt;myles> krit: So we don't need a resolution.<br>
</details>


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

Received on Monday, 10 December 2018 21:43:43 UTC