Closed Bug 1539976 Opened 5 years ago Closed 5 years ago

Unable to navigate using Arrow keys after focusing "Report a problem" in the Site Identity panel, and unable to open it

Categories

(Firefox :: Toolbars and Customization, defect, P1)

Product:
Firefox
Component:
Toolbars and Customization
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr60 --- unaffected
firefox66 --- unaffected
firefox67 --- wontfix
firefox68 --- fixed

People

(Reporter: itiel_yn8, Assigned: Jamie)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: access, regression)

STR:

  1. Open https://9gag.com/
  2. Ctrl+L > Shift+Tab > Enter > ArrowDown key until you get to "Report a problem"
  3. Try to navigate (using Arrow keys only) to the next or previous item
  4. Try to hit Enter or the spacebar

AR:
For (3), you can't navigate (back or forward) further.
For (4), nothing happens.

ER:
You should be able to navigate to the next/previous item using Arrow keys, and be able to enter it.

Tabbing to the next/previous item does work.

Has STR: --- → yes

See also bug 1522092 comment 55. This suggests "Report a problem" shouldn't be tabbable at all.

Ug. This was regressed by bug 1522092 (although that fix did prevent bug 1489874). This should be fixed by bug 1477673.

Blocks: 1522092
status-firefox67: --- → affected
Depends on: 1477673
Keywords: regression
Keywords: access
Priority: -- → P1

Assigning to Jamie so it can be closed after bug 1477673 gets fixed and is confirmed to fix this issue too.

Assignee: nobody → jteh
status-firefox67: affected → fix-optional
status-firefox68: --- → affected
Component: Site Identity and Permission Panels → Toolbars and Customization
Regressed by: 1522092
See Also: → 1539984

Fixed by bug 1477673.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED

The refactoring in bug 1477673 is probably not a good candidate for uplift, so wontfix for 67.

status-firefox67: fix-optional → wontfix
QA Whiteboard: [qa-68b-p2]
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.