Re: [csswg-drafts] [css-sizing] Stretch-fitting inline size next to floats. (#4028)

The CSS Working Group just discussed `[css-sizing] Stretch-fitting inline size next to floats.`, and agreed to the following:

* `RESOLVED: Do what Oriol says here.`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> iank_: I'm fine resolving on what Oriol has said<br>
&lt;fantasai> iank_: This is about the `stretch` keyword. It's roughly like 100%, but not quite.<br>
&lt;fantasai> iank_: Question is what to do with floats<br>
&lt;fantasai> iank_: Our guiding principle is "what does auto do here?"<br>
&lt;fantasai> iank_: and for in-flow block-level independent formatting context, what auto does here is to avoid floats<br>
&lt;fantasai> iank_: Internally, Blink doesn't actually resolve with `auto`. We map it to `stretch` or `fit-content` and then resolve that<br>
&lt;fantasai> iank_: If we did something different we'd need to add a concept<br>
&lt;fantasai> iank_: 3rd point is, being replaced counts as an independent formatting context<br>
&lt;fantasai> iank_: Therefore replaced + stretch should avoid floats<br>
&lt;fantasai> iank_: If you're not an IFC, you fill your containing block. That's what width:auto does.<br>
&lt;fantasai> iank_: When you're an atomic inline box, you stretch to the CB<br>
&lt;fantasai> iank_: Their available space, they can always grow to their CB, because they will push the line box down past the float<br>
&lt;fantasai> iank_: We don't want to diverge fit-content and stretch having different available sizes<br>
&lt;fantasai> iank_: It's the weirdest part here, but consistent because of this logic.<br>
&lt;fantasai> fantasai: Great explanation, thank you!<br>
&lt;fantasai> PROPOSED: Do what Oriol says<br>
&lt;fantasai> fantasai: Agree with the principles, that's also what we think.<br>
&lt;fantasai> RESOLVED: Do what Oriol says here.<br>
</details>


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


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

Received on Wednesday, 28 January 2026 18:59:12 UTC