- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jan 2024 13:09:44 +0000
- To: public-css-archive@w3.org
> From the bug: > > > Changing the DOM in ViewTransition.updateCallbackDone should be equivalent to changing it in the callback itself. > > Should those things be considered equivalent? Doing something after it's done shouldn't be equivalent to doing something before it's done. One of the reasons we have an `updateCallback` rather than a promise is that we don't want simple promise behaviour here. That's fair, but then it should be consistent and not racy. Right now changing the DOM in `updateCallbackDone` is *sometimes* equivalent to changing it in the update callback, which is worse than it *never* being equivalent. If the author wants a promise that always resolves after everything is captured, `transition.ready.catch()` or some such already works, no? -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9762#issuecomment-1877071353 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 13:09:46 UTC