- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Apr 2023 18:19:58 +0000
- To: public-css-archive@w3.org
I'm not sure I have anything new to provide here. I'm not a big fan of the default flex values, but that ship has long sailed. I'm also not fully-versed in all the intricacies and magics involved with the different sizing algorithms discussed - which makes it hard to comment on the difference between `min-width` of `auto` vs `min-content`. By default, I would reach for the latter - but I do not fully understand the implications of that, and would want someone to walk me through those examples more explicitly. At the higher level of my author expectations: - I do think it's fair to say that authors prioritize aspect-ratios in many/most situations where they are set. When you want an aspect ratio, there's usually a reason for it, and things often start to break when those aspect-ratios are discarded. - Flexible items with aspect ratios always have problems at their extremes, and almost always need guard-rails defined – either with min/max-widths, or queries to change the layout more dramatically. There's no one-size-fits-all answer. - In general, I would expect flex items that shrink or grow to handle their aspect-ratios in the same way. When using aspect-ratio with flexbox, I would almost never set an explicit size on the cross-axis. The whole point would be maintaining a ratio _as the item flexes_. The only reason I can imagine ending up in this situation is if I'm using flexbox to lay out non-flexible items. Either way, I would want to clarify: - If I want the items to flex, there shouldn't be an explicit height-and-ratio, I should choose one or the other. In that case, I probably also need guard-rails at the extremes. - If I don't want items to flex, the height makes some sense - but then I should turn off `flex-shrink`. Of course we need a default here, but I don't see a 'right' one. Both defaults look broken, because this is not a clear use-case - and I would want to provide a fix either way. Like I said in the call: what's important to me is that I have good options for clarifying my intent in either direction once this breaks. It would be a lot easier to comment here if any of the examples were based in actual use-cases. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6794#issuecomment-1502145518 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 April 2023 18:20:00 UTC