Re: [csswg-drafts] [css-sizing] Is the last remembered size recorded if there is size containment in a single axis? (#7529)

The CSS Working Group just discussed `Is last-remembered size recorded if size containment in single axis?`, and agreed to the following:

* `RESOLVED: "last remembered size" is tracked for the two axises independently (in case of containment in one axis), and can be invoked independently (with c-i-s:auto in one axis)`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Subtopic: Is last-remembered size recorded if size containment in single axis?<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7529<br>
&lt;fantasai> oriol: we are only storing last remembered size if there's not size containment<br>
&lt;fantasai> oriol: however, in newer specs of css-contain, we may have size containment in a single axis<br>
&lt;fantasai> oriol: what happens?<br>
&lt;fantasai> oriol: Are we still storing both width and height of last remembered size?<br>
&lt;fantasai> oriol: do we not update last remembered size in the uncontained axis?<br>
&lt;fantasai> oriol: shoudl we check at least one of the axes has size containment and then store both?<br>
&lt;fantasai> oriol: how should this work exactly?<br>
&lt;fantasai> TabAtkins: this is a very good question<br>
&lt;fantasai> Rossen_: do you have a proposal, Oriol?<br>
&lt;fantasai> oriol: maybe would feel more natural to me to do independently rather than together<br>
&lt;fantasai> oriol: right now Chromium stores together<br>
&lt;TabAtkins> q+<br>
&lt;flackr> q+<br>
&lt;fantasai> oriol: I don't have a strong opinion<br>
&lt;Rossen_> ack TabAtkins<br>
&lt;fantasai> TabAtkins: I think I lean toward tracking them together, just because say you have a set width and you have a contained block size<br>
&lt;fantasai> TabAtkins: whatever block size you want to remember, that depends on your width<br>
&lt;fantasai> TabAtkins: if you end up with a different width, your height is not going to be very meaningful<br>
&lt;fantasai> TabAtkins: it's weird to expect a different width also<br>
&lt;fantasai> TabAtkins: but I feel either record both or record neither<br>
&lt;fantasai> TabAtkins: and you need to have containment to get sizing to trigger<br>
&lt;fantasai> flackr: I was going to suggest the opposite<br>
&lt;Rossen_> ack flackr<br>
&lt;fantasai> flackr: reason beign that the only way that you have containment in one axis by it being an explicit style, whereas containment in both axes is because of content-visiblity and being off-screen<br>
&lt;fantasai> flackr: if the developer, while on screen, has containment in one axis<br>
&lt;fantasai> flackr: then it should ??? last remembered size when it goes off screen<br>
&lt;fantasai> Rossen_: that's a compelling argument<br>
&lt;fantasai> TabAtkins: that seems reasonable<br>
&lt;fantasai> Rossen_: sounds like we're approaching a resolution<br>
&lt;fantasai> Rossen_: proposed resolution is that we'll keep them separate, and store them separate<br>
&lt;fantasai> Rossen_: any objections?<br>
&lt;flackr> s/???/store the<br>
&lt;TabAtkins> RESOLVED: "last remembered size" is tracked for the two axises independently (in case of containment in one axis), and can be invoked independently (with c-i-s:auto in one axis)<br>
</details>


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


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

Received on Tuesday, 2 August 2022 14:09:50 UTC