1440570 - Policy: Define default value of "storage.local" for extensions

Status: RESOLVED WONTFIX

(Firefox :: Enterprise Policies, enhancement, P3)

Description

[YUKI "Piro" Hiroshi]

Most public extensions store their configs via the "storage.local" API, and there is no mechanism to provide default or locked value for "storage.local". There is another API "storage.managed" to provide specific values for managed environment on company use, but most addons are not designed to load values from "storage.managed". Thus a policy to define values for the local storage is required.

(Enterprise extensions should be designed for the company, but company admins not familiar to develop extensions with very limited money resource want to use major public addons as is.)

Comment 1

[YUKI "Piro" Hiroshi]

> (Enterprise extensions should be designed for the company, but company admins not familiar to develop extensions with very limited money resource want to use major public addons as is.)

This is also serious for some proprietary extensions. Actually, Adobe Acrobat 2017 extension stores its configuration via "storage.local", and there is no option to develop forked version of it.

Comment 2

[Mike Kaply [:mkaply]]

Does Chrome provide anything like this?

Comment 3

[Martin Giger [:freaktechnik]]

There is storage.managed which can be configured using the registry, I believe. See https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/storage/managed resp. https://developer.chrome.com/extensions/manifest/storage

Comment 4

[Mike Kaply [:mkaply]]

Yes, but the extensions have to be changed to explicitly use it.

I think this is probably WONTFIX though.

Comment 5

[Mike Kaply [:mkaply]]

If extensions want to do this, they should use storage managed.