Repository navigation
Keep presence avatars visible in compact navigation and back off retries - #1626
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.
Compact navigation hid span-based presence avatar triggers along with action labels, even while presence continued working. Limit that rule to action-button labels so avatars remain visible and clickable.
Also respect recovery-secret 429 cooldowns (Retry-After, with a 60-second fallback) and progressively back off failed WebRTC edges up to 60 seconds. Repeated discovery notifications cannot bypass an active retry timer. An unreadable workspace now reports a read failure without claiming that another device has its data.
Validation: 55 focused unit/component tests plus app and library type checks passed on refreshed develop. The two-tab Chromium presence/follow test passed against the local app at 320px, with a separate visible avatar/menu check. This does not certify cross-network staging behavior or identify the original slowdown's cause.
The full frontend unit suite also passed locally (1,157 tests, using source aliases to avoid stale workspace build artifacts and disabling Node 26 experimental web storage).