- From: Oriol Brufau via GitHub <noreply@w3.org>
- Date: Sat, 28 Mar 2026 15:21:41 +0000
- To: public-css-archive@w3.org
> E.g. the web-developer has placed an explicit width on the element, we should respect that. Disagree. If `width: min-content` produces a certain width, then `min-width: min-content` should enforce that same size as a minimum. No different than here: ```html <div style="width: min-content; border: solid">Foo</div> <div style="width: 0; min-width: min-content; border: solid">Foo</div> ``` > Compute the "block content" size - compute the block-size of the replaced element, ignoring the block-lengths And also ignoring inline-lengths, right? Otherwise this would be 0x0: ```html <canvas width="50" height="50" style="width: 0; min-width: min-content; height: 0px; min-height: max-content; border: solid magenta"></canvas> ``` > "inline min/max content" sizes are treated as unresolvable/indefinite Fair, no need to resolve a tentative inline size to the stretch size or the default object with of 300px. So even if #12333 resolves to have the inconsistency between replaced and non-replaced, stretchable replaced can be treated as non-replaced in this regard. That is, webkit-based option 1 from OP is still reasonable. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13149#issuecomment-4148253411 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 28 March 2026 15:21:42 UTC