- From: Adam Argyle via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Sep 2022 20:23:41 +0000
- To: public-css-archive@w3.org
I personally expect `aspect-ratio` to be a strong request, aka one that can cause overflow in some cases. Though, while exploring this I've learned otherwise.. that in many cases `aspect-ratio` can be a weak request. I assume I'd have to do extra work to tell a `1/1` box to not be a box anymore inside a flex container, because it's been clearly requested to be a box and if I want something else out of that layout relationship I'll need to go be more specific. But currently, it seems the other way around, where I have to go be more specific about unflexing the child so that it'll be a box again / be the `aspect-ratio` I authored. I generally like, or have come to peace with, flexbox's adjustment of children, but do feel that an `aspect-ratio` should have higher precedence over flexbox. -- GitHub Notification of comment by argyleink Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6794#issuecomment-1238613548 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 September 2022 20:23:43 UTC