Open Bug 1809934 Opened 2 years ago Updated 1 year ago

Invoke extension interfaces in tabs.

Categories

(Firefox for Android :: WebExtensions, enhancement, P5)

Firefox 110
All
Android
enhancement

Tracking

()

Tracking Status
firefox121 --- affected
firefox122 --- affected
firefox123 --- affected

People

(Reporter: zn7esutb, Unassigned)

Details

(Whiteboard: [qa-triaged])

User Agent: Mozilla/5.0 (Android 11; Mobile; rv:109.0) Gecko/110.0 Firefox/110.0

Steps to reproduce:

Extensions frequently create new tabs, as most appear to, in order to invoke their configuration and/or authentication pages.

Actual results:

This is problematic on Fenix, because extensions are (for an unknown strange reason) invoked in a new interface which solely supports the current page and a back button. That back button navigates intents rather than URLs, which means that navigating out of the extension's interface and into the new authentication tab can break the authentication pipeline.

It also has a myriad of alternative obvious problems – no way to activate extensions, no refresh button, in fact, no interface whatsoeve

Expected results:

Extension interfaces should be invoked in tabs. On desktop, extensions that this could be useful for provide a button to open in a new tab, but on Fenix, the apparently intent-based back button means that even this partial remedy is inadequate.

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)
Flags: needinfo?(cpeterson)
Severity: -- → N/A
Priority: -- → P5

I'll confirm this issue because it is still reproducible on all builds, but I'll mark this as an enhancement.

Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
Whiteboard: [qa-triaged]
You need to log in before you can comment on or make changes to this bug.