Uh oh!
There was an error while loading. Please reload this page.
feat(web): canonical keyboard traversal and focus rings - #41434
Conversation
Lean on native browser keyboard navigation across the trace viewer and recorder UI: - TabbedPane tabs become real <button>s: every header is a Tab stop, Space/Enter selects. This also gives the snapshot Action/Before/After tablist keyboard navigation, which it was missing. - CodeMirror no longer captures Tab/Shift-Tab, so focus is not trapped in source/network/locator/aria editors. - Add :focus-visible rings (keyboard-only) to tabs, toolbar buttons, text/search inputs, toolbar selects, and CodeMirror editors. Fixesmicrosoft#41422
Test results for "MCP"1 failed 7379 passed, 1122 skipped Merge workflow run. |
Test results for "tests 1"2 failed 3 flaky49007 passed, 1142 skipped Merge workflow run. |
72601df
into
microsoft:mainUh oh!
There was an error while loading. Please reload this page.
Aditya Kumar Gupta (triemerge)
commented
Jun 23, 2026
Nice approach, i think the html-reporter might have the same gap with its own |
Summary
TabbedPanetabs real<button>s so every header is a native Tab stop and Space/Enter selects — this also gives the snapshot Action/Before/After tablist the keyboard navigation it was missing.Tab/Shift-Tab, so focus is no longer trapped inside source/network/locator/aria editors.:focus-visiblerings to tabs, toolbar buttons, text/search inputs, toolbar selects, and CodeMirror editors.Fixes#41422