perf: reduce tab close lag by optimizing lifecycle middleware#3746
Open
Vanashreeshankar wants to merge 1 commit intofastrepl:mainfrom
Open
perf: reduce tab close lag by optimizing lifecycle middleware#3746Vanashreeshankar wants to merge 1 commit intofastrepl:mainfrom
Vanashreeshankar wants to merge 1 commit intofastrepl:mainfrom
Conversation
👷 Deploy request for hyprnote pending review.Visit the deploys page to approve it
|
✅ Deploy Preview for hyprnote-storybook canceled.
|
Author
|
4 tasks
This file contains hidden or 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
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.
Summary
Improves tab-close responsiveness by optimizing lifecycle middleware logic.
What changed
This PR implements Priority 2 and Priority 3 optimizations described in #3547:
Impact
These changes result in an estimated ~13–16% improvement in perceived tab-close performance, especially when closing multiple tabs in quick succession.
Scope & rationale
Priority 1 batching of middleware updates was intentionally left out to keep the change focused, low-risk, and easy to review. Existing behavior, restore logic, and navigation history remain unchanged.
Verification