Closed
Bug 1521627
Opened 6 years ago
Closed 6 years ago
incognito support in storage api
Categories
(WebExtensions :: General, defect, P1)
WebExtensions
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mixedpuppy, Unassigned)
References
(Blocks 1 open bug)
Details
Need to look at what can be done here.
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(lgreco)
Comment 1•6 years ago
|
||
The storage APIs and their results are never associated to a particular browser window or tab, and so I think that they should not require any special "filtering" for the WebExtensions incognito modes.
As an additional proof of that, the storage APIs are explictly mentioned in the Chrome docs related to the "incognito split mode" as the only APIs that are not behaving differently even in that scenario, from "https://developer.chrome.com/extensions/manifest/incognito#how-to-choose":
chrome.storage.sync and chrome.storage.local are always shared between regular and incognito processes
And so I think that we may just close this bugzilla issue as "resolved,worksforme" or "resolved,invalid".
Flags: needinfo?(lgreco)
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•