- From: Claudia Meadows via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 May 2025 19:57:57 +0000
- To: public-css-archive@w3.org
> > Question: are updates held until after the callback resolves or until after the promise resolves? > Until after the promise returned by the update callback resolves. Okay, good. Means I don't need to add some bolded warnings about knock-on effects in the docs as part of it. (Sorry for the sloppy wording there, I meant "until after the callback resolves or until after the transition completes".) > OK, what's stopping you now? :) Just a bit of design work. 😉 > Understood. As I said, it's in interop 2025 so it's likely to be implemented in Gecko and WebKit before any other change we propose here. Yeah, that translates to us probably not going to be able to switch to `window.navigation.*` until around 2030, unfortunately. Async generators only just recently got enough browser support for me to feel comfortable depending on them, to give you an idea about lead times. (I'm planning, for the next major iteration of Mithril, to build on a baseline of 2020.) -- GitHub Notification of comment by dead-claudia Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12125#issuecomment-2855783839 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 May 2025 19:57:58 UTC