Open Bug 1328946 Opened 7 years ago Updated 2 years ago

[a11y] Keyboard navigation in Computed View: have to press Tab several extra times

Categories

(DevTools :: Inspector, defect, P3)

defect

Tracking

(firefox53 affected)

Tracking Status
firefox53 --- affected

People

(Reporter: jryans, Unassigned)

References

Details

(Whiteboard: [a11y_2020])

+++ This bug was initially created as a clone of Bug #1327790 +++

>>>   My Info:   Win7_64, Nightly 53, 32bit, ID 20161219030207 (2016-12-19)
STR_4:
1. Open url   data:text/html,<style>*{background:transparent
2. Open devtools -> computed view
3. Type "background-attachment" in filter field, press Tab 2 times to focus checkbox "Browser styles"
4. Press Tab
5. Press Tab

AR:
 Step 4 - the actual rule is focused (can't press Enter to open it)
 Step 5 - the actual rule is focused
ER:
 The actual rule should be focused in Step 5. What do you think?
Inspector bug triage (filter on CLIMBING SHOES).
Priority: -- → P3
These 3 bugs (bug 1328943, bug 1328944, bug 1328946) were originally filed by arni2033 as bug 1327790.
It doesn't look like they will live well separately (w/o somebody working specifically on
accessibility in devtools (For example, Yura Zenevich)),
and it doesn't seem that there was a good reason to resolve original report as Invalid.
After all, reporter of that bug was concerned about usability, not about stealing bugs.

The correct way to track a meta bug is to keep it open until all blocking bugs are resolved.
Product: Firefox → DevTools

(In reply to J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow) from comment #0)

+++ This bug was initially created as a clone of Bug #1327790 +++

My Info: Win7_64, Nightly 53, 32bit, ID 20161219030207 (2016-12-19)
STR_4:

  1. Open url data:text/html,<style>*{background:transparent
  2. Open devtools -> computed view
  3. Type "background-attachment" in filter field, press Tab 2 times to focus
    checkbox "Browser styles"
  4. Press Tab
  5. Press Tab

AR:
Step 4 - the actual rule is focused (can't press Enter to open it)
Step 5 - the actual rule is focused
ER:
The actual rule should be focused in Step 5. What do you think?

This should really be a VirtualizedTree component. It takes care of most if not all keyboard accessibility as well as the semantics.

Priority: P3 → P5
Priority: P5 → P3
Whiteboard: [a11y_2020]
Component: Inspector: Computed → Inspector
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.