Repository navigation
fix(web): preserve navigation layout and write state - #325
Merged
Merged
Conversation
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.
Home now reuses observed card content heights when exact dimensions and style/class fingerprints still match, retaining the measurement fallback and Back geometry. Private WeakMap registration preserves early-paint markup. Leaving a page closes its popovers immediately so nested previews are disposed without waiting for invisible closing animations; same-page dismissal still animates.
Write controls describe their dialog behavior while permission discovery or key approval is pending. A follow confirmed by the first hand-off check keeps its new follower count when the reader was known not to follow beforehand. Previously that fast confirmation was mistaken for an action that already existed.
Validation:
The original production post-opening sample was 126.2 ms; its exact cause remains unproven. Bounded per-attempt diagnostics retain sanitized hover/resource/frame/task evidence after the original assertions. The selected card, 600 ms hover, original click-to-post expression, replies assertion and <100 ms budget remain unchanged. The older intermittent Wasm trap also had no retained underlying stack; lifecycle assertions now retain error stacks.
Exact-head CI and normal main deployment/performance checks remain required before final production verification.