Enabling first party isolation breaks WebExtension IndexedDB storage
Categories
(Core :: Storage: IndexedDB, defect, P2)
Tracking
()
People
(Reporter: arantius, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Steps to reproduce:
User reported issue: https://github.com/greasemonkey/greasemonkey/issues/3045#issuecomment-509805392
Install Firefox, install Greasemonkey, install at least one user script. Enable first party isolation and the script (everything stored in IndexedDB, which includes that) disappears.
Updated•5 years ago
|
Seems that this happens with every extension that uses IDB: extension data is stored in "storage\default\moz-extension+++MYGMID" & "storage\default\moz-extension+++MYGMID^userContextId=MYCONTID", but as soon as FPI is enabled, it's storing its data "storage\default\moz-extension+++MYGMID^firstPartyDomain=MYGMID" without any migration.
This means: if FPI is enabled during the extension installation, the extension data is saved in the FPI location. If FPI is deactivated later on, a completely new storage is used and all extension data seems to be gone for the user. This is insane :(
Updated•5 years ago
|
Updated•5 years ago
|
Description
•