[css-view-transitions-1] What should we do if someone skips the view transition when flushing the previous update callbacks #11943
Comments
|
I'm a bit confused about the problem here. Can you elaborate on the scenario? 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. |
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:
I want to make sure the "Flush the update callback queue" never skips the current view transition.
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. |
|
The issue is the acrop |
|
Err... The issue is the script skipping the transition you're just about to do the capture for |
|
It seems at the very least we should check the transition state again after flushing the queue right? |
Ah I see |
|
Perhaps the call to "flush the update callback queue" should move to the beginning of https://drafts.csswg.org/css-view-transitions-1/#perform-pending-transition-operations-algorithm |
|
Yes, I think that'd be a sensible thing. |
…ther view-transition operations This ensures that a DOM update callback that skips the active transition would take effect. Closes w3c#11943
This is more like a question because I don't have a testcase for this.
Per the recent update of the spec in 7.3. Setup view transition:
The step 2, "flush the update callback queue" runs the scripts, so I'm thinking is it possible that script skips the current view transition we are setting up? It's impossible to call
skipTransition()API in the previous update callbacks to skip the new view transition, so all I can think of is to change the visibility of the document. However, the change of visibility of the document queues a DOM task so it may happen after we setup the current view transition. However, I'm not sure if there are any other ways to skip the view transitions. (But it sounds like possible?)So is it possible that someone skips the current view transition in previous update callbacks when we setup the current view transition? If it is possible, what is the expected behavior here?
cc @noamr and @emilio
The text was updated successfully, but these errors were encountered: