- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Mar 2024 19:07:00 +0000
- To: public-css-archive@w3.org
One note is that the current spec draft just defines `calc-size()` and doesn't say which properties accept it. I think we do need to agree on which properties accept it. I think the list is probably something like this: * `width`, `height`, [`block-size`, `inline-size`](https://drafts.csswg.org/css-logical-1/#dimension-properties) (intrinsic sizing keywords and `auto`) * `min-width`, `min-height`, `min-block-size`, `min-inline-size` (intrinsic sizing keywords and probably `auto`) * `max-width`, `max-height`, `max-block-size` `min-block-size` (intrinsic sizing keywords but *not* `none`) * [`flex-basis`](https://drafts.csswg.org/css-flexbox/#flex-basis-property) (intrinsic sizing keywords and `auto` and `content`??) * the `<track-breadth>` and `<inflexible-breadth>` productions for [`grid-template-rows` and `grid-template-columns`](https://drafts.csswg.org/css-grid-1/#track-sizing) (`min-content` and `max-content` and, for the latter, `auto`) * I don't think there's a need to allow `fr` units in `calc-size()` since they already allow math. (It could be nice for completeness but it also doesn't feel worth it.) (My current prototype has just been for `width`, `height`, `min-width`, `min-height`, `max-width` and `max-height`.) It's not clear to me whether the grid or flex parts have important use cases, though. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-2025918637 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 March 2024 19:07:01 UTC