-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document "rendering suppression for view transitions" also suppresses "perform pending transition operations" #10186
Comments
Tangentially related concern from @mattwoodrow :
|
The flow goes like this:
So in essence, activating the transition doesn't necessarily happen in "perform pending transition operations", so it won't be blocked by the suppression flag. The suprression is to freeze the rendering while the new state is updating during the course of the author provided update callback. Happy to discuss/clarify this further. |
Ah thanks. I think confusion came from the fact that the first definition you see in the CSS spec for "rendering suppression for view transitions" mentions redirecting hit-testing, which I (sensibly?) assumed would be done the duration of the whole view transition. Perhaps the concept could be renamed to detail more precisely why rendering is being suppressed in the context of VT |
@noamr @khushalsagar What is this rendering suppression supposed to avoid? |
It ensures the browser is not rendering frames while the author is asynchronously updating the DOM to the new state. |
What is the issue with the HTML Standard?
It would only run
"perform pending transition operations"
once then for the next rendering update loop, the document would be filtered outThe text was updated successfully, but these errors were encountered: