Implement "chrome.storage.managed"
Categories
(WebExtensions :: Storage, defect, P5)
Tracking
(firefox67 verified, firefox68 verified)
People
(Reporter: ido.y, Assigned: mkaply)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete, Whiteboard: [design-decision-approved][triaged])
Attachments
(3 files)
Updated•9 years ago
|
Comment 2•9 years ago
|
||
Comment 3•9 years ago
|
||
Comment 4•9 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Comment 6•8 years ago
|
||
Updated•8 years ago
|
Assignee | ||
Comment 8•8 years ago
|
||
Comment 9•8 years ago
|
||
Updated•8 years ago
|
Comment 11•8 years ago
|
||
Comment 12•7 years ago
|
||
Comment 13•7 years ago
|
||
Comment 14•7 years ago
|
||
Updated•7 years ago
|
Updated•6 years ago
|
Comment 15•6 years ago
|
||
Assignee | ||
Comment 16•6 years ago
|
||
Assignee | ||
Comment 17•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 18•6 years ago
|
||
Assignee | ||
Comment 19•6 years ago
|
||
Assignee | ||
Comment 20•6 years ago
|
||
Assignee | ||
Comment 21•6 years ago
|
||
When this patch lands, this page:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage/managed
Needs to be updated.
Comment 22•6 years ago
|
||
Comment 23•6 years ago
|
||
bugherder |
Assignee | ||
Comment 24•6 years ago
|
||
Attached are files for testing this bug.
There is a policies.json that sets the value in policy.
There is a simple extension that can be loaded via about:debugging.
After loading, you can debug the extension and view the console and see that the value you set in policy is displayed in the console.
Comment 25•6 years ago
•
|
||
This issue is verified as fixed on Firefox 68.0a1(20190319095054) and Firefox 67.0b3(20190318154932) under Win 7 64-bit and Mac OS X 10.14.1.
Please see the attached screenshot.
Comment 26•5 years ago
|
||
This issue is tracked here: mdn/sprints #1430
Comment 27•5 years ago
|
||
Is the message here that this is a new way to allow managed installation of web extensions, or should it be discussed as the preferred way because it makes it easier to create cross-browser extensions? Is the existing Firefox managed storage method going away or is it going to remain as an alternative?
These probably seem like stupid questions, but I don't want to give the wrong message.
Assignee | ||
Comment 28•5 years ago
|
||
I would call it a new way. The API (chrome.storage.managed) is the same.
We didn't implement it originally via policy because we didn't have policy.
We have no plans to remove the JSON option.
Comment 29•5 years ago
|
||
Confirming the documentation requirements:
- new manifest key page for
storage
with the propertymanaged_schema
in line with https://developer.chrome.com/apps/manifest/storage - update to storage.managed to note that, on Firefox, the content of managed storage can be defined optionally by the
managed_schema
to provide compatibility with Chrome. (Firefox will continue to support arbitrary json in manage storage, without a schema).
Assignee | ||
Comment 30•5 years ago
|
||
We're actually not using the managed_schema concept at all. For us, it's just a matter of doing the right thing in a policies.json file or GPO.
you can see an example here:
https://github.com/mozilla/legacy-browser-support/blob/master/README.md
Comment 31•5 years ago
|
||
A new page has been added to MDN to describe the storage manifest key, with compatibility data pending in PR 5575. Please let me know if any further changes are needed.
Updated•2 years ago
|
Description
•