3 ms·
chrome.storage docs: "Confidential user information should not be stored! The storage area isn't encrypted." https://developer.chrome.com/extensions/storage htt
by spenvo 11y ago
chrome.storage docs: "Confidential user information should not be stored! The storage area isn't encrypted." https://developer.chrome.com/extensions/storage https://developer.chrome.com/extensions/storage
- jaredsohn 11y agoI was intending to just dispute that 'the blocked list would be "in the open" to other extensions'. Why couldn't you use chrome.storage.local or the background page's localStorage? Either should protect the data from other extensions and not expose it to third parties.
- spenvo 11y agoI wanted explicit language from Chrome's docs about how it scopes storage. Firefox provided it: "The simple storage module exports an object called storage that is persistent and scoped to your add-on." https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_APIs/simple-storage https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_A... But all Chrome's docs said were the previously mentioned warning about not using it to store confidential user info. So, to answer your question: caution Actually, if you go back to my init commit on Github - you can see that I originally used the chrome.storage API. I extricated it from the code - except for the non-sensitive settings