tabs.duplicate does not immediately make the duplicated tab active
Categories
(WebExtensions :: General, defect, P5)
Tracking
(firefox79 fixed)
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: ke5trel, Assigned: perso)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tabs])
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Comment 1•7 years ago
|
||
Updated•7 years ago
|
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Duplicate of bug 1394376
Comment 5•5 years ago
|
||
(In reply to ariasuni from comment #4)
Duplicate of bug 1394376
Not a duplicate. In that bug it became possible to prevent a tab from becoming active, which does indeed address the concern from comment 1 here, but it doesn't fix the reported bug.
This bug is about the switching to occur too late.
As you may have noticed, the implementation in ext-tabs.js waits for a content restoration event, supposedly to work around a bug:
https://searchfox.org/mozilla-central/rev/3262e013550a0db7c1840a78a3878a929801fe40/browser/components/extensions/parent/ext-tabs.js#1104
This bug could be resolved by activating before that event is fired, either by doing so immediately after tab duplication, or through a new option (aOptions is very useful ;) ).
Do you want to look into this and attach a patch?
Updated•5 years ago
|
Updated•5 years ago
|
Comment 8•4 years ago
|
||
bugherder |
Description
•