Open Bug 1843862 Opened 1 year ago Updated 1 year ago

The keyboard navigation focus is lost after activating the developer warning panel

Categories

(Toolkit :: Picture-in-Picture, defect)

Desktop
All
defect

Tracking

()

Accessibility Severity s3
Tracking Status
firefox-esr115 --- disabled
firefox115 --- disabled
firefox116 --- affected
firefox117 --- affected

People

(Reporter: danibodea, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Note

  • note1

Found in

  • Beta v116.0b5

Affected versions

  • Nightly v117.0a1
  • Beta v116.0b5

Tested platforms

  • Affected platforms: all
  • Unaffected platforms: none

Steps to reproduce

  1. Load https://codepen.io/niklasbaumgardner/pen/MWBjBeZ
  2. Use keyboard navigation to focus the PIP URL button and activate it.
    a. CTRL+L to focus the URL bar
    b. ESC to dismiss the URL drop-down
    c. TAB to focus the PiP/Bookmarks group
    d. ENTER to activate button
  3. TAB twice to focus the "Activate anyway" toggle button.
  4. ENTER to switch the toggle to enabled.
  5. ESC to dismiss the developer warning panel.

Expected result

  • The keyboard navigation focus falls back on the PiP URL button.

Actual result

  • The keyboard focus navigation is lost.
  1. TAB once

Actual result

  • The keyboard navigation focus is shown on the Firefox View button.

Regression range

  • not a regression, but a flaw since implementation.

Additional notes

  • This issue does not occur if the user focuses the "Learn more" link and then presses ESC to dismiss the developer warning panel; in this case, the focus correctly falls on the URLbar PiP button.
Summary: The keyboard navigation focus is lost after activating the developer waring panel → The keyboard navigation focus is lost after activating the developer warning panel

:danibodea, if you think that's a regression, could you try to find a regression range using for example mozregression?

Accessibility Severity: --- → s3
You need to log in before you can comment on or make changes to this bug.