Closed
Bug 1796319
Opened 3 years ago
Closed 3 years ago
Add-on settings opened in a new tab everytime
Categories
(Firefox for Android :: WebExtensions, defect, P2)
Tracking
()
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | verified |
People
(Reporter: gl, Assigned: rsainani)
References
Details
(Whiteboard: [fxdroid])
Attachments
(2 files)
From github: https://github.com/mozilla-mobile/android-components/issues/6424.
Prerequisites
- Privacy Badger is installed and enabled in Fenix
Steps to reproduce
- Open Fenix.
- Navigate to "Settings-> Add-ons-> Privacy Badger".
- Tap the "Settings" button.
- Repeat the steps above and notice the open tabs.
Expected behavior
The page is redirected to the "Privacy Badger Options" tab.
Actual behavior
Another identical page is opened in a new tab.
Device information
- Android device:
-Samsung Galaxy A5(2016) (Android 7.0)
-Samsung Galaxy S7 Edge (Android 8.0.0)- Fenix version:
- 3/26 Nightly build (#20861010)
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(cpeterson)
Updated•3 years ago
|
Severity: -- → S3
| Assignee | ||
Updated•3 years ago
|
Assignee: nobody → rsainani
Updated•3 years ago
|
Whiteboard: [fxdroid]
Updated•3 years ago
|
Updated•3 years ago
|
Flags: needinfo?(cpeterson)
Priority: -- → P2
Summary: [Bug] Add-on settings opened in a new tab everytime → Add-on settings opened in a new tab everytime
Comment 2•3 years ago
|
||
Comment 3•3 years ago
|
||
| Assignee | ||
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox110:
--- → fixed
Flags: qe-verify+
Resolution: --- → FIXED
Comment 4•3 years ago
|
||
Hello,
Verified as fixed on the latest Nightly from 21th of December 2022 (110.0a1).
Tested on Google Pixel 6 (Android 13).
Thanks!
Updated•3 years ago
|
| Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•