Closed
Bug 1352189
Opened 7 years ago
Closed 7 years ago
Creating a tab of a deleted container is permitted
Categories
(WebExtensions :: General, defect, P2)
Tracking
(firefox57 fix-optional)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox57 | --- | fix-optional |
People
(Reporter: jkt, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: triaged)
When I use: browser.tabs.create({url: confirmUrl, cookieStoreId: `firefox-container-2`}) Where I have deleted container 2, the browser opens the tab in a non container, I personally think this should be an exception as it might make developers easily open up privacy issues where they didn't check the containerId. In my own use case it actually makes the code a lot more complex as I don't currently have the contextualIdentities api. The contextualIdentities api coming in 53 will allow me to check for this however I would prefer to reduce code complexity and errors. I would also push for using the userContextId instead of/also for creating tabs and referencing them.
Reporter | ||
Comment 1•7 years ago
|
||
I forgot to mention the created tab actually has the correct cookieStoreId rather than default. This prevents me implementing the fix for this in web extensions in 52.
Updated•7 years ago
|
Priority: -- → P2
Whiteboard: triaged
Reporter | ||
Updated•7 years ago
|
Blocks: ContextualIdentity
Comment 2•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Reporter | ||
Comment 4•7 years ago
|
||
Yeah I think this got fixed with the changes in 57. Lets close this.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jkt)
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•