- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Mon, 28 Jul 2025 23:19:07 +0000
- To: public-css-archive@w3.org
@yisibl thanks for the additional use case. If we end up resolving `width: 100%` against the parent available space (per the suggestion in the issue description), that will result in one column in this case, which likely isn't desirable. In the following demo (this will need to be rendered in a Chromium browser with chrome://flags/#css-masonry-layout enabled), the img tags similarly have `width: 100%`, but they also have a containing `div` around each photo that has a `min-width: 100px` that constrains the auto columns to be at least 100px, producing a more desirable result. https://microsoftedge.github.io/Demos/css-masonry/syntax-examples/default-track-size.html <img width="832" height="242" alt="Image" src="https://github.com/user-attachments/assets/39162d8a-1221-4140-b448-4a5350cbb66a" /> So, I think in this case, some sort of width constraint is needed to accomplish what an author would be looking under this track definition. @tabatkins any thoughts on the case @yisibl provided wrt replace elements? > Currently the img width in Chrome is equal to 0.5px, which is not expected anyway. Yeah, that sounds like a bug, I'll investigate that to see how we are producing that result. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12432#issuecomment-3130107695 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 July 2025 23:19:08 UTC