Open Bug 1485563 Opened 6 years ago Updated 3 years ago

[mac] Hover state easily mistaken as keyboard selection in AS context menus

Categories

(Firefox :: New Tab Page, defect, P3)

All
macOS
defect

Tracking

()

Tracking Status
firefox61 --- affected
firefox62 --- affected
firefox63 --- affected
firefox91 --- affected

People

(Reporter: asoncutean, Unassigned)

Details

(Keywords: uiwanted)

Attachments

(1 file)

Attached video screencast issue.mov
[Affected versions]: 
- 61.0.2 (20180807170231)
- 62.0b19 (20180820172315)
- 63.0a1 (20180821220101)

[Affected platforms]:
- macOS 10.13 /10.12
- Ubuntu 16.04 x64

[Steps to reproduce]:
1. Open a New Tab page 
2. Open the context menu of the Top Sites section
3. Scroll the page using the keyboard’s arrows

[Expected result]:
- None of the context menu options are selected while the scrolling action takes place.

[Actual result]:
- Options are selected one at the time, pressing the Enter key doesn’t trigger any response for any of them.

[Regression range]: 
- I will try to determine one asap.

[Additional Notes]:
- Context menu of Highlights/ Recommended by pockets section shows similar behavior.
- On Ubuntu platform a glitch is triggered around the first two options.
- This issue is not reproducible on Windows platforms.
Rectification:

The issue is visible only on mac platforms, due to invisible cursor behavior. Two more conditions are needed to trigger this confusing situation: 
  - When the section context menu is opened, the user is still able to use the page keyboard navigation (e.g. the up & down arrow keys, as exemplified in the screencast)
  - The highlight function has the same UI design for both keyboard navigation and mouse hover. On Mac, when the user navigates through the keyboard, the pointer disappears and creates the illusion of keyboard selection instead of mouse hover. The user is misled to press the Enter key in order to access the option highlighted in that specific moment. That isn’t possible because the above specified option is in hover state, not selected.

This way, the option seems non-functional, confusing the end user. 

A possible workaround: as long as the section context menu is opened (and also in focus), only the navigation inside the context menu should be possible.
OS: All → Mac OS X
Summary: Nonfunctional selected context menu options are triggered when scrolling the New Tab page with the keyboard arrows → [mac] Hover state easily mistaken as keyboard selection in AS context menus
Not a regression, this behaviour is reproducible since the beginning of section context menus implementation.
Keywords: uiwanted
Priority: -- → P3
Component: Activity Streams: Newtab → New Tab Page

Still reproducible with Mac 10.14, Nightly 91.0a1 2021-07-05. Due to low impact and visibility, setting S4 severity.

Severity: normal → S4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: