- From: Boris Chiou via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Mar 2025 21:44:15 +0000
- To: public-css-archive@w3.org
> Can you elaborate on the scenario? Sorry, this is more like a question because I was trying to make sure we don't have to worry about the case if any script skips the current view transition we are setting up. This means in the step 2: > 1. Let document be transition’s relevant global object’s associated document. > 2. [Flush the update callback queue](https://drafts.csswg.org/css-view-transitions-1/#flush-the-update-callback-queue). I want to make sure the "Flush the update callback queue" **never** skips the current view transition. > I don't see an inherent problem with the script that runs as part of a DOM update skipping a newer transition, and this was possible before. Yes, this is my question. Just wonder if it is possible after your update. Thanks for the feedback. Close this issue because we don't have to worry about this case. -- GitHub Notification of comment by BorisChiou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11943#issuecomment-2727012968 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 March 2025 21:44:16 UTC