- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Mar 2025 20:55:16 +0000
- To: public-css-archive@w3.org
One edge case that we need to clarify... Our above-quoted resolution was conditioned on `When aspect-ratio is non-initial` What about **non-initial** values of `aspect-ratio` that **behave like the initial value**? (The spec says that "[degenerate](https://drafts.csswg.org/css-values-4/#degenerate-ratio)" aspect ratios (those involving 0 or infinity) [behave the same as the initial value](https://drafts.csswg.org/css-sizing-4/#valdef-aspect-ratio-ratio) "and, generally, won’t do anything"). I tend to think those should behave as the initial value for this new behavior as well (i.e. we should still return `0` from getComputedStyle). The point of our resolution here is that we want `getComputedStyle(elem).minWidth` and `minHeight` to return `auto` **in the cases where there's a meaningful aspect-ratio** and the automatic minimum size is potentially going to do something interesting. -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11716#issuecomment-2755726914 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 March 2025 20:55:16 UTC