Repository navigation
Remove conversation-row ellipses and retain accessible options - #690
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.
Message-exchange conversation rows still showed an ellipsis after PR #687, while normal chat rows lacked an explicit keyboard menu route. Remove the row ellipsis and retain the existing source-specific actions through right-click, Control-click, Shift+F10 and the Context Menu key. A shared Selected conversation options button preserves tap access; menus support arrow keys, Home/End, Escape, accessible states and focus return without selecting another conversation.
This completes the remaining gap in native task
#V#task_agent_f435fd48e1e1819b72951fdbaea78ca3. PR #687 already delivered compact headers, icon-only submit modes, actor-scoped browser preferences and transient feedback; those implementations are retained.Validation: 48 targeted Jest tests across five suites; frontend static lint; diff checks; Chromium with production template/styles/modules at 320, 448 and 1280 pixels for row routes, preserved reference copying, menu bounds, list collapse/reopening and accidental-selection checks. The existing header/composer replay also passes at desktop, phone and landscape sizes. Evidence is retained in
.run/header-submit-reconciliation/in the controller-owned task worktree.Browser evidence uses isolated deterministic transport. It does not claim public authentication, physical mobile/macOS devices or a manual screen-reader session. No deployment is requested; the task explicitly treats the screenshot deployment note as context only.