- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jun 2020 22:27:25 +0000
- To: public-css-archive@w3.org
@cbiesinger In [that example](https://github.com/w3c/csswg-drafts/issues/5032#issuecomment-649109809) if we go with the logic in https://github.com/w3c/csswg-drafts/issues/5032#issuecomment-639874263 then `min-width: min-content` will resolve as the size under min-content constraint, which considers `height: 100px` and the aspect ratio to yield `min-width: 100px`. The final width would then be 100px. (If we decide instead that `min-content` always takes the content’s size, then it would be 200px.) I think one principle we need to make more explicit here is that resolving keyword sizes in a given axis requires ignoring all sizing properties in that axis, but might take into account sizing properties in the other axis due to an interdependency caused by layout rules or aspect-ratio. (The min/max clamps are applied after all sizing properties in that axis are resolved to a length.) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5032#issuecomment-651402662 using your GitHub account
Received on Monday, 29 June 2020 22:27:27 UTC