[tracking] APIs to control behavior after tab closing
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: robert_abc3, Unassigned)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Keywords: meta)
Updated•6 years ago
|
From what I understand, extensions that want to control which tab to activate after closing must listen to multiple tab
events, calling browser.tabs.moveInSuccession()
or browser.tabs.update()
all the time. This could be simplified if we had something like onBeforeTabClose
so that extensions could set successorTabId
just before the tab is removed.
Right before tab closing is the only moment extensions need to set successorTabId
, it's not optimal that they need to track every onActivated
, onMoved
, onRemoved
, onUpdated
just because there's no way to anticipate that the tab is about to close.
Comment 2•3 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=1419947#c3 and nearby comments; one of the design inputs that led to browser.tabs.moveInSuccession
was the constraint that closing a tab shouldn't block on any calls out to extensions before the next tab is activated.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•