- From: Ian Kilpatrick via GitHub <noreply@w3.org>
- Date: Tue, 31 Mar 2026 21:22:59 +0000
- To: public-css-archive@w3.org
> I guess Blink's ComputeMinMaxSizes doesn't include aspect-ratio nor these fallbacks either? Depends on the context. The algorithms ComputeMinMaxSizes doesn't include aspect-ratio. It's handled centrally for non-replaced. `min-size:auto` makes this somewhat necessary. Its also better cache wise. https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/block_node.cc;l=1024-1037;drc=16d85a1427f61d06aba1ff4b60340e11c1ac6b6f We just pass a lambda into the various length resolving functions to determine how to resolve these things. We do it this way so that don't need the (complex?) logic to determine if we need a min/max content size upfront (we are lazy). We previously had them separate (e.g. a "NeedsMinMaxContentSize" function), but was very easy to get out of sync. For the "initial" block-sizes min-content/etc is just indefinite and can proceed from there. See: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/length_utils.cc;l=1099-1136?q=file:length_utils.cc&ss=chromium -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13149#issuecomment-4165673053 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 March 2026 21:23:00 UTC