tab.active is always false in in-App browser
Categories
(GeckoView :: Extensions, defect)
Tracking
(firefox137 ?, firefox138 affected, firefox139 affected)
People
(Reporter: eight04, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:139.0) Gecko/20100101 Firefox/139.0
Steps to reproduce:
- Install Firefox Nightly for Android.
- Download and install the extension: https://github.com/eight04/webextension-test/archive/refs/heads/tab-active.zip. You may have to configure the developer mode and
xpinstall.signatures.required
to install extension from zip. - Install Flipboard App: https://play.google.com/store/apps/details?id=flipboard.app
- Start Flipboard -> select some topics -> skip login.
- Open an article.
- Click the page.
Actual results:
The extension will print the information/events of the tab. Although the tab is visually "activated", tab.active
is always false
and onActivated
is never called.
Expected results:
Not sure. I think:
tab.active
should be true when opened in an in-App browser.- The tab of in-App browser should have a different
windowId
.
Is there a way to detect such in-App browser tabs? So we can exclude these tabs from the extension.
Comment 1•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Tabs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 months ago
|
||
Hello,
I reproduced the issue on the latest Nightly for Android (139.0a1/20250413210718) and Beta for Android (138.0b6/20250411092217) on an Oppo Reno6 5G running Android 13.
The information printed by the extension on the article opened in Flipboard does indeed show the active
parameter as always false
and there is no instance of onActivated
being called.
Opening the same article in the browser and clicking the page will also print out the information, however, the active
parameter is true
and onActivated
is called once (from what I can see there is one instance where ”type”: “tabActivated”
was printed).
Comment 3•2 months ago
|
||
The severity field is not set for this bug.
:007, could you have a look please?
For more information, please visit BugBot documentation.
Updated•5 days ago
|
Updated•5 days ago
|
Updated•5 days ago
|
Description
•