Open Bug 1584214 Opened 5 months ago Updated 3 months ago

Netmonitor - TAB navigation - Focus ring appears inside Headers section instead of next element

Categories

(DevTools :: Netmonitor, defect, P3, minor)

defect

Tracking

(firefox-esr60 unaffected, firefox-esr68 wontfix, firefox67 wontfix, firefox68 wontfix, firefox69 wontfix, firefox70 wontfix, firefox71 wontfix, firefox72 fix-optional)

Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- wontfix
firefox67 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- fix-optional

People

(Reporter: cfogel, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Affected versions

  • 68.1.0esr, 69.0.1, 70.0b9, 71.0a1 (2019-09-23);

Affected platforms

  • Windows 10, Ubuntu 18.04, macOS 10.13.6;

Steps to reproduce

  1. Launch Firefox, access any webpage;
  2. Open DevTools, Netmonitor and click on any request from the list;
  3. Click on the Headers tab;
  4. Press the TAB key.

Expected result

  • there is no focus ring for the section, TAB focuses next element;

Actual result

  • TAB-ing from the Headers section title shows the focus ring for the whole section;
  • another thing worth mentioning is the z-index for the collapsible sections;

Regression range

  • First bad: build_date: 2018-11-13
  • Last good: build_date: 2018-11-13
  • Pushlog: URL
  • Potential regressor: bug 1503554

Additional notes

  • attached screenshot with the main issue;
  • same issue for other sub-sections as well; the Security sub-section has a collapsible element that can be toggled but the focus ring is still on the whole sub-section;
  • the Response and Params sub-sections require 2x TABs to show the focus ring;
  • the Stack Trace sub-section has an expected behavior, as in the focus jumps on the next element and not the whole section;
Has Regression Range: --- → yes
Has STR: --- → yes

Thanks for the report!

I can reproduce this on my machine.

This might be similar to the issue described in bug 1581283

Honza

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.