fix(nuxt): trigger immediate DOM update on page:finish
#22566
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
#22334, #22560
β Type of change
π Description
When updating the DOM from head changes, we batch the changes, this reduces DOM thrashing. We use this batching when the page is finishing which is causing the linked issue.
However, we can just update the head immediately.
One issue with this solution though is the
page:finish
is now delayed, on average this is ~10ms for a few DOM updates (if needed), so maybe worth considering if this change is worth it.π Checklist