1213475 - Complete the implementation of chrome.storage

Status: RESOLVED FIXED

(WebExtensions :: General, defect, P2)

Description

[Andy McKay]

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.

Comment 1

[Mihail Diordiev]

Also chrome.storage.local.clear is not implemented.

Comment 2

[Johann Hofmann [:johannh]]

I made a new bug (bug 1217886) for implementing chrome.storage.local.clear

Comment 3

[Mihail Diordiev]

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.

Comment 4

[Mihail Diordiev]

(In reply to Mihail Diordiev from comment #3)
> Another critical difference is that in Chrome extensions 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.

Comment 5

[amaslo]

(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

Comment 6

[Martin Riethmayer]

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).

Comment 7

[Andy McKay]

All the blockers are closed, but interestingly not bug 1230802, which may or may not get implemented.