Complete the implementation of chrome.storage

RESOLVED FIXED

Status

()

Toolkit
WebExtensions: General
P2
normal
RESOLVED FIXED
2 years ago
2 months ago

People

(Reporter: andym, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [storage]triaged)

(Reporter)

Description

2 years ago
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

2 years ago
Also chrome.storage.local.clear is not implemented.
Depends on: 1217886
I made a new bug (bug 1217886) for implementing chrome.storage.local.clear
(Reporter)

Updated

2 years ago
Flags: blocking-webextensions-

Comment 3

2 years ago
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 hidden (spam)

Comment 5

2 years ago
(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
Depends on: 1197346
Depends on: 1220494

Updated

2 years ago
Blocks: 1214733
(Reporter)

Updated

a year ago
Whiteboard: [storage] → [storage]triaged

Comment 6

10 months ago
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).
Blocks: 1303905
(Reporter)

Updated

9 months ago
Component: WebExtensions: Untriaged → WebExtensions: General
Flags: blocking-webextensions-
Priority: -- → P2
(Reporter)

Updated

5 months ago
No longer blocks: 1214733
No longer blocks: 1303905
(Reporter)

Comment 7

2 months ago
All the blockers are closed, but interestingly not bug 1230802, which may or may not get implemented.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.