Open
Bug 1355646
Opened 9 years ago
Updated 3 years ago
Consider extending browsingData to add update/move method
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(firefox55 affected)
NEW
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | affected |
People
(Reporter: jkt, Unassigned)
References
Details
(Whiteboard: [browsingData][triaged])
As a follow up to 1353726 it would be nice to add the ability to move stores from one cookieStoreId to another.
The use case is a logged in user wants to keep their sessions to a website whilst moving into a different container or out of private browsing mode.
browser.browsingData.move(
{cookieStoreId: "firefox-default"},
{cookieStoreId: "firefox-container-1"},
{cookies: true, history: true, formData: true, cache: true, ...}
);
This might become even more useful if first party isolation has the same cookieStoreId API.
As :andym mentioned this is a lot more contentious than the first proposal.
Updated•9 years ago
|
Priority: -- → P3
Whiteboard: triaged
Updated•9 years ago
|
Whiteboard: triaged → [browsingData][triaged]
Updated•7 years ago
|
Product: Toolkit → WebExtensions
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•