Open
Bug 1763916
Opened 3 years ago
Updated 1 year ago
Fix webextension tab events when adoptTab fails
Categories
(WebExtensions :: Frontend, defect, P3)
WebExtensions
Frontend
Tracking
(Not tracked)
ASSIGNED
People
(Reporter: Oriol, Assigned: Oriol)
References
(Blocks 1 open bug)
Details
See detailed STR in bug 1762800 comment 0.
Using gBrowser.adoptTab
to move a tab into a new window may not succeed (e.g. bug 1758307).
In that case,
- When
gBrowser.adoptTab
attempts to move, webextensions receive anonDetached
event on the old window, and anonAttached
event in the new one. - When
gBrowser.adoptTab
aborts, webextensions receive anonRemoved
event on the new window. - This utterly confuses extensions, making them think that the tab was moved and then removed, but actually it's still in the original window! E.g. my Tab Counter Plus is affected.
I guess that no event should be fired at all. Or at least, after the first onDetached
/onAttached
pair, when the adoption fails fire these events again in reverse, as if the tab moved forth and back.
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:mixedpuppy, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(mixedpuppy)
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Comment hidden (off-topic) |
Comment 3•3 years ago
|
||
Sorry, there was a problem with the detection of inactive users. I'm reverting the change.
Assignee: nobody → oriol-bugzilla
Status: NEW → ASSIGNED
Updated•1 year ago
|
Flags: needinfo?(mixedpuppy)
You need to log in
before you can comment on or make changes to this bug.
Description
•