Closed
Bug 1324375
Opened 8 years ago
Closed 8 years ago
Clarify behavior of tabs.remove() Promise when beforeunload blocks removal
Categories
(Developer Documentation Graveyard :: Add-ons, defect)
Developer Documentation Graveyard
Add-ons
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ke5trel, Unassigned)
Details
Documentation states tabs.remove() returns:
> "A Promise that will be fulfilled with no arguments when the tab(s) have been removed."
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/tabs/remove
In Firefox 53 the Promise is fulfilled after the beforeunload response even when the user chooses to stay on the page and the tab is not removed.
Possible wording:
> "A Promise that will be fulfilled with no arguments when the tab(s) have been removed
> or the user chooses to stay on the page(s)."
Note that this differs from Chrome 55 where the callback returns immediately without waiting for the beforeunload response but this means the developer cannot distinguish between user-initiated and programmatic tab closure.
Comment 1•8 years ago
|
||
move to dev doc component - we are OK with that wording change proposal
Flags: needinfo?(sescalante)
Updated•8 years ago
|
Component: WebExtensions: Untriaged → Add-ons
Product: Toolkit → Developer Documentation
Updated•8 years ago
|
Flags: needinfo?(sescalante)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•