- From: Bramus Van Damme <bramus@google.com>
- Date: Mon, 26 Sep 2022 09:34:20 -0400
- To: Jeremy Morton <jez9999@gmail.com>
- Cc: W3C style mailing list <www-style@w3.org>
Received on Monday, 26 September 2022 13:34:43 UTC
Hi Jeremy, Could you please file an issue in the csswg-drafts repository for this?* (URL: https://github.com/w3c/csswg-drafts/issues <https://github.com/w3c/csswg-drafts/issues>)* That’s the place where discussions happen nowadays. Thanks, Bramus. On Sat, Sep 24, 2022 at 8:07 AM Jeremy Morton <jez9999@gmail.com> wrote: > It would be nice to be able to do this: > > #menuToggle input~#menu { > /* Hide menu */ > display: none; > transition: display 0ms 0.5s; > } > #menuToggle input:checked~#menu { > /* Display menu */ > display: unset; > transition: display 0ms 0ms; > } > > A major thing CSS transitions are lacking right now is the ability to > transition "binary" properties such as display, where there is no > clear way to gradually transition them. However, this doesn't mean it > wouldn't be useful to be able to simply delay their being changed. > Being able to slide a pure CSS menu off the page, for example, is > currently supported, but it then needs to be set to display:none to > take it out of the document flow. When this is specified as a > transition, the transition should simply do nothing until the delay > has passed and then transition instantly. > > -- > Best regards, > Jeremy Morton (Jez) > > >
Received on Monday, 26 September 2022 13:34:43 UTC