Repository navigation
Use down-arrow for Messages replies and label latest navigation - #720
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.
The Messages reply composer showed a text Send button alongside a down-arrow used for transcript navigation. Replace the reply label with a down-arrow in its existing position, with an accessible Send message name and a pending ellipsis. Label transcript navigation Latest message so its separate action is clear.
Validation: 24 targeted Jest tests passed, covering send failures/retries, pending duplicate suppression and reply context. Playwright exercised the actual Messages component and CSS with synthetic HTTP responses at 390px and 1280px: send-by-arrow, minimum 44px target, draft-preserving latest navigation, and existing unread pagination checks passed. Desktop/mobile screenshots inspected; evidence retained in
.run/message-arrow/. This is fixture browser evidence, not live authenticated acceptance. No deployment requested.Native task: #V#task_agent_c244524646710c9806872992aa127293.
Merge decision: ready on this bounded Tier 1 evidence; no observed material regression.