Consider extending browsingData.RemovalOptions to allow removal by cookieStoreId

NEW
Unassigned

Status

()

Toolkit
WebExtensions: General
P3
normal
20 days ago
14 days ago

People

(Reporter: jkt, Unassigned)

Tracking

52 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [browsingData][triaged])

(Reporter)

Description

20 days ago
For the containers experiment we are getting requests for the ability to behave like private tabs in certain circumstances or move from one container to another.

Adding the ability to do the following:
browser.browsingData.remove(
  {cookieStoreId: "firefox-default"},
  {cookies: true, history: true, formData: true, cache: true, ...}
);

For moving to another container we actually might need (this might need a separate bug though):

browser.browsingData.move(
  {cookieStoreId: "firefox-default"},
  {cookieStoreId: "firefox-container-1"},
  {cookies: true, history: true, formData: true, cache: true, ...}
);

This would allow a website to move it's data from one context to another cleanly.
(Reporter)

Updated

20 days ago
Summary: Consider extend browsingData.RemovalOptions to allow removal by cookieStoreId → Consider extending browsingData.RemovalOptions to allow removal by cookieStoreId

Comment 1

14 days ago
The move is probably more contentious, could you move that to a seperate bug. The ability to pass a cookieStoreId to browsingData makes sense though, we should do that.
Priority: -- → P3
Whiteboard: [browsingData][triaged]
(Reporter)

Updated

14 days ago
See Also: → bug 1355646
You need to log in before you can comment on or make changes to this bug.