1901775 - [Android Large Screen Optimized Tier 2] Some home screen UI elements lack hover state with an external mouse

Status: NEW

(Firefox for Android :: Homepage, defect, P3)

Description

[Adina Petridean QA [:apetridean]]

Attachment: homescreen.mp4

Steps to reproduce

1. Open Fenix App.
2. Go to the Fenix homescreen.
3. Using an external mouse, hover over certain buttons (3-dots menu, tabs tray)
4. Observe the behavior.

Expected behavior

When using an external mouse, actionable UI elements from the homescreen display hover state to indicate interactivity.

Actual behavior

The actionable UI elements ( 3dots menu and tabs tray) do not display hover state when using an external mouse.

Device information

Android device model/OS: Samsung Galaxy S23 Ultra (Android 14)
Fenix Version: Nightly Fenix 129.0.a1 (from 11.06.2024)

Any additional information?

Chrome shows hover state when an external mouse is used.

Comment 1

[Delia Pop (Android QA)]

Attachment: Nightly_ToolbarRedesign.mp4

On the latest Nightly 130.0a1 from 07/29 with the Toolbar Redesign feature enabled, the 3-dot menu does not display hover state when using an external mouse, both in browser and in custom tab.
Tested with Google Pixel 8 Pro (Android 14).

Comment 2

[Chris Peterson [:cpeterson]]

P3 because we don't need this bug in our current sprint.

Comment 3

[Petru-Mugurel Lingurar [:petru]]

For performance reasons we're temporarily removing some ripples - bug 1915975
Moving this ticket to be re-evaluated when we're closer to the release of the navbar.

Comment 4

[Joe M [:jmahon]]

Refinement notes:

• Some uncertainty about how much control we have over this in the Android system, and whether this is needed.

[:Channing], can you reevaluate if this is actually needed for the Toolbar work? You can follow up with Zac and Roger for more info.

Comment 5

[Joe M [:jmahon]]

(In the meantime, I'm going to remove it as a release blocker unless you add it back deliberately)

Comment 6

[Channing]

(In reply to Joe M [:jmahon] from comment #5)

(In the meantime, I'm going to remove it as a release blocker unless you add it back deliberately)

No this is not a release blocker.