mirror of
https://github.com/vector-im/element-call.git
synced 2026-09-22 22:29:30 +00:00
fkwpandClaude Opus 5
b82b0a889c
The menu focuses whatever the pointer is over, so `:focus-visible` was being asked a question it cannot answer. Chromium calls every focus after any key press keyboard-driven, so one Escape left the border following the mouse for the rest of the session; Firefox never calls a programmatic focus keyboard-driven, so the border never appeared there at all. Neither is what D13 asks for. The menu now notes which of the two reached the current item, and the border follows that. Nothing existing covers this: Compound exports no such helper, the repo has no react-aria, and Radix marks both modalities alike. `:focus-visible:not(:hover)` would hide the border under the cursor but still leave Firefox without one. Two acceptance criteria named checks that could not fail for the reason they exist. AC24 was manual and now names an e2e test that reads the painted outline as the pointer and keyboard take turns. AC15 asserted the attribute its stylesheet keys off rather than the greying, and now names the meter's own story; deleting the CSS rule fails that story and not the unit test. Both edits made with the owner's authorisation. Spec: FEATURES_SPEC/2026-09_Audio_Quick_Menu.md — AC15, AC24. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>