- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jan 2024 12:31:37 +0000
- To: public-css-archive@w3.org
> It's worth checking with @domenic or @annevk on this. Adding microtask checkpoints to solve race conditions is usually a bad smell. Agreed, would love to find a more elegant way around this if this is indeed a spec bug. > > In userland, promises don't shuffle the order of reaction callbacks, or provide a way to do this. > > Could you document some of the bugs you're seeing as a result of the current behaviour? There could be another solution. The context is https://bugs.chromium.org/p/chromium/issues/detail?id=1513887 I've noticed that when running `startViewTransition` inside a `navigate` event, I can't update the new state inside an `updateCallbackDone` callback, my promise reactions are handled after the state is already captured, wasn't sure if this is an implementation or a spec thing. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9762#issuecomment-1877023185 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 January 2024 12:31:39 UTC