Closed Bug 1213475 Opened 4 years ago Closed 3 years ago
Complete the implementation of chrome
The methods on the API are: https://developer.chrome.com/extensions/storage Currently implemented: local To be implemented: Types StorageChange StorageArea Properties sync managed Events onChanged The sync property sounds exciting.
Also chrome.storage.local.clear is not implemented.
I made a new bug (bug 1217886) for implementing chrome.storage.local.clear
Another critical difference is that in Chrome extension we have access from the content script to the chrome.storage, but in Firefox WebExtensions not. Is this on purpose or should be implemented? My user case: In the options page users specify for each urls to enable the extension. This data is stored in chrome.storage, then when loading the content script, I check whether the current url is in the storage array.
(In reply to Mihail Diordiev from comment #3) > Another critical difference is that in Chrome extension we have access from > the content script to the chrome.storage, but in Firefox WebExtensions not. > Is this on purpose or should be implemented? Access from content script is already requested in this ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=1197346
I think https://bugzilla.mozilla.org/show_bug.cgi?id=1301098 may have been better reported in here, sorry, I didn't find this entry at the time of writing. TLDR: If I'm not mistaken, chrome.storage.local is not working on option pages (or is in contrast to what the documentation says).
Component: WebExtensions: Untriaged → WebExtensions: General
Priority: -- → P2
All the blockers are closed, but interestingly not bug 1230802, which may or may not get implemented.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.