Popup UI for add-ons not accessible from homescreen
Categories
(Fenix :: WebExtensions, enhancement)
Tracking
(firefox120 affected)
| Tracking | Status | |
|---|---|---|
| firefox120 | --- | affected |
People
(Reporter: will.j.ginsberg, Unassigned)
References
Details
(Whiteboard: [qa-triaged])
Attachments
(1 file)
|
2.32 MB,
video/mp4
|
Details |
Steps to reproduce:
- Open firefox for android
- Tap the 3 dot menu
- Tap "Add-ons"
Actual results:
Add-ons manager opens. I am unable to open the options UI for any add-on.
Expected results:
A menu showing "Add-ons Manager" and each installed add-on appears. Tapping any addon opens its options page.
The above behaviour is what I see when I follow these steps:
- Open firefox for android
- Navigate to any website
- Tap the 3 dot menu
- Tap "Add-ons"
|
Reporter | |
Updated•7 months ago
|
|
||
Comment 1•7 months ago
|
||
Hi, thanks for reporting. I was not able to reproduce the issue described on Nightly 120.0a1 and RC 118.2.0 with Google Pixel 7 PRO (Android 14) and Samsung Galaxy S9 ( Android 8).
In order to further look into the issue you're experiencing, could you please provide the following additional information?
Details regarding the Device used, OS, Android version;
Is this bug occurring consistently, or is it intermittent?
Is this bug reproducible on the latest Nightly (120-0a1 )?
Could you please share a video with this issue?
Thanks!
|
|
||
Updated•7 months ago
|
|
|
Reporter | |
Comment 2•7 months ago
|
||
|
|
Reporter | |
Comment 3•7 months ago
|
||
Attached a recording of this behaviour in 120-0a1. I am using a Pixel 3 running android 12.
|
||
Comment 4•7 months ago
|
||
Because homescreen is not an actual tab. See bug 1809833.
|
|
||
Comment 5•7 months ago
|
||
Thank you Will! After watching the video, I was able to reproduce this issue with Google Pixel 7 PRO on the latest Nightly from 112.0a1. According to the comment above, this issue is occurring because the home screen is not the actual tab.
|
|
||
Updated•7 months ago
|
I think this should be "upgraded" from feature request to bug.
Or do we need a new bug: "browserAction button invisible if on home page"?
Consider all the new users first time installing FF on Android because of the addons, then they load an addon, and then there is no way to start it - that is a show stopper for all new users. It effectively blocks using the addons which were just opened to the public.
How should anybody guess that there needs to be an opened "real" tab for the addon actionButton to be visible? How should a normal user guess that the home page is not a tab? And why should the visibility of the browserActionButtons be related to the fact whether a tab is opened?
The actionButton might be what actually opens the first tab in FF on Android if FF is newly installed and the user wants to try the addon feature. Or for users who clean their interface (close all tabs after use) and then cannot start addon tabs, because they are on the homepage?
Being on homepage or not should not affect the visibility of the browserAction buttons.
Description
•