Load earlier messages for most-recent-unread navigation - #675
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
1 participant
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.
The unread count can include messages outside the loaded page, while the conversation pane previously offered navigation only for loaded unread messages. “Jump to most recent unread” now stays available for a counted unread message in earlier pages, loads backwards until it finds the target, and scrolls and focuses the newest unread contribution.
Loading failures retain a retryable action; stale counts report that no unread messages remain. Navigation stops when the conversation or organisation changes and does not bulk-acknowledge skipped messages.
Validation: 16 message-exchange tests passed, covering multi-page navigation, retry, stale counts, conversation switching and existing visible-read behaviour. A further 24 related message-panel tests passed (40 tests total). Static frontend lint and diff checks passed. Chromium with production modules/CSS and synthetic HTTP pagination passed at 390px and 1280px, verifying target focus and viewport visibility. This is fixture acceptance, not live authentication testing. No deployment requested.
Von task: #V#task_agent_cb08f17a9888e9d74b3da4e01667b8a8.