- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Nov 2023 00:15:11 +0000
- To: public-css-archive@w3.org
As this is a bit of an expansion in complexity, it might be useful to justify myself a little more directly. ^_^ We want to solve the "animate `height: auto` to `height: 0` use-case. But we don't want to solve *just* that case; there's reasonable nearby use-cases that should be similarly solveable. Adding special magic *just* for the auto->0 case and leaving the rest as impossible is bad for authors and violates the core premise of the Extensible Web Manifesto. (And we'll probably be solving those nearby cases later, anyway, so might as well make sure we can get them right today, if possible.) In particular, the two nearby use-cases I think are vital are 1. "animate *any* height to `height: 0;`". Ideally without having to know what the other height even *is*, so you can write a generic "shrink to zero" animation for your `<details>` elements and it'll work everywhere, regardless of what starting height you gave it. 2. "animate `height: auto` to `height: 50px;`" (or any other non-zero, definite value). It's pretty obvious that shrinking to zero won't always be the right thing to do in any given case. My proposal is, as far as I can tell, nothing more than the minimum functionality required to solve those two cases, and then epistemically closing over that functionality so we have a consistent feature set. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1800681714 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 November 2023 00:15:13 UTC