1876928 - On Pixel 7a, in landscape, Firefox will not display menu when pressing meatballs button

Status: RESOLVED FIXED

(Fenix :: Toolbar, defect)

Description

[anthony]

Steps to reproduce:

Launch firefox..
Open a website..
Have phone in portrait
Tap meatballs - menu appears
Close menu
Rotate phone to landscape
Tap meatballs
Phone / app acknowledges tap by brief highlight, does not show menu.

Android Firefox 122.0 Build 2015998391 b49c4f2380+ GV: 122.0-20240118164516 AS 122.0.1 2024-01-18T22:17:07.663185936

Plugins installed:

• uBlock Origin
• Dark Reader

Phone:
Google Pixel 7a

OS:
Android 14 - 5 Jan 2024 security update

No software/hardware android menu keys (back / home etc.) but gesture driven

Actual results:

Menu does not appear when tapping meatballs in landscape when a website is showing.

Expected results:

Menu should appear, regardless of landscape or portrait mode, or if website loaded.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:tthibaud, could you have a look please?

For more information, please visit BugBot documentation.

Comment 2

[Vasilica Tamas QA [:vtamas]]

Attachment: pixel7menuissue.mp4

Hi Anthony! Thanks for reporting this issue! I was able to reproduce it on Firefox Nightly 124 from 2024-02-16 using a Pixel 7 with Android 13.

It seems to be an old regression but I cannot reproduce it on Firefox RC 123.0.
Regression range: Last Good Nightly [2023-05-11] - First Bad Nightly [2023-05-12].

Comment 3

[Dianna Smith [:diannaS]]

I suspect the reason the regression range is from 2023-05-12 is because the functionality was introduced in bug 1816517/bug 1816558 on that date. However, the Tabs tray to Compose feature is only enabled in Beta as of Fx121 by Bug 1815002, which is why you probably could not reproduce it in Firefox RC 123.0. It wont be enabled in Release until bug 1815003.

NI'ing :007 and setting the regressor as 1815002. Feel free to correct any mistakes/assumptions I might have made.

Comment 4

[Noah Bond [:007]]

This has to do with the Toolbar and not the Tabs Tray, so I'm removing the regressor and updating the component. (The tickets listed above are for the three-dot button at the top of the Tabs Tray).

Are any of the buttons in the Toolbar clickable? Is it just the three-dot button that is unresponsive?

ccing Mike in case he has any information here, as he has been working in this part of the codebase recently.

Comment 5

[anthony]

With FF 123.0 20160003223 f5f378e2c0+ GV 123.0-20240212203859 AS: 123.0.1 2024-02-12T02:56:20.620455103 ... if I move to landscape, and open a new tab with the Firefox home screen (recently visited etc.) is showing, then meatballs will work.

As soon as I navigate to a page in landscape, the meatballs won't work.

The following I can still do in landscape:

• Select the tab menu (the box in the number to the right of the address bar).
• Select the address bar and enter a search or URL.
• Click the home button.

It appears that it's just the meatballs that's broken in landscape.

Comment 6

[Mira Lobontiu (Android QA)]

I was not able to reproduce this on the latest Fenix Nightly 128.0a1 from 5/21 with Google Pixel 6 (Android 14), nor with Google Pixel 8 (Android 14).
We will verify also on a Google Pixel 7 device as soon as possible.

Comment 7

[Lorand Janos]

We tried reproducing this issue on a Google Pixel 7 Pro (Android 14) and with a Google Pixel 7 (beta 2 version of Android 15) without success.
The menu is displayed correctly in landscape mode on all the tested devices with the latest Nightly build (2024-05-22).

Comment 8

[Mihai Adrian Carare [:mcarare]]

Closing as per comments above.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Comment 10

[Donal Meehan [:dmeehan]]

:mcarare do you know what fixed this in nightly?
Lorand, is it still reproducible in Fx127 Beta and Fx126 Release?

Just trying to clean up the metadata here

Comment 11

[Mihai Adrian Carare [:mcarare]]

This should have been initially fixed by the patch for 1854131. Because that caused a regression in another scenario, 1891729 was opened. The fix for that should not have regressed this, so I added QA to re-check it.

Comment 12

[Lorand Janos]

The issue is not reproducible on the latest RC 126.0 and latest Beta 127.0b4 builds, using the same Google Pixel 7 device with the beta 2 version of Android 15.
The menu is displayed correctly, with or without the mentioned extensions installed.