- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Thu, 15 Jan 2026 18:35:32 +0000
- To: public-css-archive@w3.org
Just got back around to playing with the proposal to always use min instead of max for orthogonal items in a row container. With my original example, we would now get <img width="82" height="74" alt="Image" src="https://github.com/user-attachments/assets/1dd00f76-70c9-48dd-aefd-a40118b649ef" /> so the container is large enough to fit everything and underflows since some items lay out at their max instead of min. @Loirooriol in the example you provided, we create even larger overflow with my proposal: <img width="190" height="129" alt="Image" src="https://github.com/user-attachments/assets/e0096a04-6078-4069-aaac-c9ca19710dd1" /> Which seems to be because when we lay out the items for real, they grow to fill the row size, and that ends up being larger than the item's min-content size in some cases (which is what is being used during the compute min/max pass on the container with this proposal). Which now leads me to wonder if we need to run an actual layout pass (not forcing items to min or max) to ensure a more accurate result in these cases and avoid overflow. Or do we accept that some rare cases will be the exception like this one. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13116#issuecomment-3756316243 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 January 2026 18:35:33 UTC