- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Dec 2023 20:20:02 +0000
- To: public-css-archive@w3.org
> The CSS Working Group just discussed `[css-transitions] Transition to height (or width) "auto"`, and agreed to the following: > > * `RESOLVED: Add calc-size() to css-values-5 and work out details there` I've debated posting this for a few days, since I don't want to be *that* person. š First, Iām not sure a resolution that happens after the official telcon end time is valid. I, for one, had to drop as I had a hard stop at the top of the hour, and I suspect I'm not the only one. More substantively, and I guess with my TAG hat on, I have serious reservations about the usability implications of this. The rationale seems to revolve entirely around implementation details, rather than author-facing usability, which is a bit of a design smell. How would you explain to authors why and when they'd need `calc-size()` instead of simply `calc()`? If you'd explain it as "you use this instead of `calc()` when you have an intrinsic sizing keyword", then the natural next question is, why can't the UA make this transformation under the hood, rather than authors having to learn a new function? While the pain point is definitely pervasive and worth solving, adding many similar features to the language to solve subtly different problems is a classic antipattern, and severely hampers learnability. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1869754533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 December 2023 20:20:04 UTC