Closed
Bug 1395932
Opened 7 years ago
Closed 7 years ago
IndexedDB does not work even for WebExtension background page in private browsing mode
Categories
(Core :: Storage: IndexedDB, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1313401
People
(Reporter: feedbro.reader, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36
Steps to reproduce:
Firefox supports WebExtensions (like Chrome). IndexedDB is a great storage for storing and querying lots of data in the WebExtension code. This happens in the "background page" of the WebExtension.
Actual results:
When the user uses Firefox in "Private Browsing" mode, IndexedDB does not work even for the WebExtension background page (open() call throws InvalidStateError). It is logical that IndexedDB cannot be used by normal webpages but it should be 100% available and usable for extension background page. Otherwise all extensions relying on that API will break.
Further, this "feature" can be used to detect if user is in private browsing mode which is not ideal.
This is a separate issue than 781982 which is more related to normal web pages.
Expected results:
WebExtension background pages should be always able to use IndexedDB fully even in private browsing mode. Mozilla Add-on review process should ensure that extensions won't do anything that would leak information or compromise security.
For the record, this also happends with the "do not remember history" setting .
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•