Re: [csswg-drafts] [css-sizing-4] Clarify spec about when elements are allowed to not have a last remembered size (#6220)

The CSS Working Group just discussed `[css-sizing-4] Clarify spec about when elements are allowed to not have a last remembered size`, and agreed to the following:

* `RESOLVED: When laying out an element, if contain-intrinsic-size is not auto, remove last-remembered-size immediately`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-sizing-4] Clarify spec about when elements are allowed to not have a last remembered size<br>
&lt;emeyer> github: https://github.com/w3c/csswg-drafts/issues/6220<br>
&lt;emeyer> oriol: Followup on FTF discussion<br>
&lt;emeyer> …If an element is not generating a box, if the intrinsic size isn’t auto, the last remembered size will be forgotten<br>
&lt;emeyer> …You can take a look at my comment in the issue<br>
&lt;Rossen_> q?<br>
&lt;jensimmons> present-<br>
&lt;emeyer> …When we are laying out an elem,ent, it’s a good time to observe or not observe an element, but I have to observe an element to see if I should forget last remembered size and then unobserve it<br>
&lt;emeyer> …Makes more sense to say with c-i-s stops being auto, we should immediately remove last remembered size (l-r-s)<br>
&lt;emeyer> …Some were arguing against that, argument is that it’s not well defined what should happen<br>
&lt;emeyer> …I don’t see a big problem and would prefer to switch to a more consistent behavior<br>
&lt;emilio> +1 to oriol, the undefinedness of flushing layout/style info is https://github.com/w3c/csswg-drafts/issues/5115 and very long-standing<br>
&lt;emeyer> TabAtkins: no opinions, I need to talk about this more with Ian to see what’s what<br>
&lt;emeyer> emilio: We have a long-standing bug about this, I think the c-i-s is probably not the place to draw the line<br>
&lt;emeyer> …I think I agree with oriol, we should do this whenever we style the document and can re-evaluate whether elements need l-r-s<br>
&lt;emeyer> Rossen_: What’s the one-line resolution?<br>
&lt;emeyer> oriol: When laying out an element, if c-i-s is not auto, remove l-r-s immediately<br>
&lt;emeyer> TabAtkins: no objections now, but want to preserve right to object later<br>
&lt;emeyer> Vladimir: Does this interact badly with container queries?<br>
&lt;emeyer> oriol: Not sure, to be honest. Will have to think about that.<br>
&lt;emeyer> emilio: The remembered size doesn’t affect stlying, but does affect layout. I think you need size containment to cause this<br>
&lt;emeyer> …I don’t think it’s a problem but worth thinking about a bit more<br>
&lt;emeyer> Rossen_: Doesn’t sound like a strong pushback, and we can bring this back if we have issues down the line<br>
&lt;emeyer> RESOLVED: When laying out an element, if contain-intrinsic-size is not auto, remove last-remembered-size immediately<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 17 August 2022 16:38:12 UTC