RESOLVED FIXED 208549
Web Inspector: AXI: can't leave Styles and Computed panels by pressing Tab
https://bugs.webkit.org/show_bug.cgi?id=208549
Summary Web Inspector: AXI: can't leave Styles and Computed panels by pressing Tab
Nikita Vasilyev
Reported 2020-03-03 17:04:14 PST
Once the focus is inside of the Styles or Computed panel, it's trapped there. You can't escape the panel by pressing Tab. Focus cycles inside the panel. Steps: 1. Open Styles panel. 2. Focus on the filter field at the bottom of the sidebar. 3. Press Tab. Expected: Focus moves forward to "Classes" toggle button. Actual: Focus "cycles" back to the top of the sidebar - to the "Active" checkbox. Steps: 1. Focus on the first checkbox - "Active". 2. Press Shift-Tab. Expected: Focus moves to "Styles" sidebar tab. Actual: Focus moves to the filter field at the bottom of the sidebar.
Attachments
Patch (3.15 KB, patch)
2020-03-03 17:18 PST, Nikita Vasilyev
hi: review+
Patch (3.24 KB, patch)
2020-03-05 16:28 PST, Nikita Vasilyev
no flags
Radar WebKit Bug Importer
Comment 1 2020-03-03 17:04:34 PST
Nikita Vasilyev
Comment 2 2020-03-03 17:18:59 PST
Devin Rousso
Comment 3 2020-03-05 16:19:40 PST
Comment on attachment 392354 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=392354&action=review r=me > Source/WebInspectorUI/UserInterface/Views/GeneralStyleDetailsSidebarPanel.js:419 > + if (event.shiftKey && this._panel.focusLastSection) { Why not mimic `_handleForcedPseudoClassCheckboxKeydown` and have `if (event.key !== "Tab" || !event.shiftKey)` instead? That way, `if (this._panel.focusLastSection)` lines up quite nicely with the `this._panel.focusLastSection();` on the next line :)
Nikita Vasilyev
Comment 4 2020-03-05 16:28:38 PST
WebKit Commit Bot
Comment 5 2020-03-05 16:47:03 PST
Comment on attachment 392645 [details] Patch Clearing flags on attachment: 392645 Committed r257959: <https://trac.webkit.org/changeset/257959>
WebKit Commit Bot
Comment 6 2020-03-05 16:47:05 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.