- From: Psychpsyo (Cameron) via GitHub <noreply@w3.org>
- Date: Sat, 14 Mar 2026 00:53:02 +0000
- To: public-css-archive@w3.org
> I find it hard to understand why a basic view-related requirement would need to be implemented using JavaScript. I believe this is the responsibility of CSS itself. For example, in the implementation of a collapsible drawer menu, we always want the menu to appear smoothly from the side. We could naturally use `transition` to control this process. However, if we don't set `display: none`, we will still retain this element in the document flow, and even if the element is not in the view, then `Tab` can still jump to the menu. This is why `@starting-style` exists, and its counterpart is `@ending-style`. It's been said in this thread before, but for cases where you just want to set `display: none` instead of removing the node entirely, this is already solved by `transition-behavior: allow-discrete`, which lets you transition to and from `none`. (The element stays in the non-`none` state for the whole transition instead of flipping at the midpoint.) -- GitHub Notification of comment by Psychpsyo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9500#issuecomment-4058989301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 14 March 2026 00:53:03 UTC