-
Notifications
You must be signed in to change notification settings - Fork 435
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
fix(core): skip updating focusPath state if unchanged #7524
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Sep 19, 2024 9:14 AM (UTC) ✅ All Tests Passed -- expand for details
|
juice49
approved these changes
Sep 23, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
As seen in the chart below, the commit that merged #6370 had severe impact on editor FPS.
The reason for this is that #6370 reverted an earlier PR that, among other things, skipped updating focusPath state in DocumentPaneProvider if the emitted focusPath was (deeply) equal to the current focus path. This, in combination with the portable text input emitting onFocus on selection change, which is emitted from the portable text editor on every keystroke, triggered excessive re-renders even in cases where the focus path did not really change.
This fixes the issue by skipping the state update if focus-path hasn't changed. Instead of taking the handed focusPath as-is, it gets it from the pool of existing focus paths, which returns a stable instance for equal paths.
Relevant benchmarks.
Note:
body
is the Portable Text array here. Higher is betterBefore
After (higher is better)
What to review
Does the change make sense?
Testing
Should be covered by existing tests.
Notes for release