Open
Bug 1363856
Opened 8 years ago
Updated 2 years ago
[meta] Implement WebExtensions API to give access to specific preferences
Categories
(WebExtensions :: General, enhancement, P3)
WebExtensions
General
Tracking
(Not tracked)
NEW
People
(Reporter: bsilverberg, Unassigned)
References
(Depends on 4 open bugs)
Details
(Keywords: meta, Whiteboard: triaged)
There are a number of preferences to which some popular legacy add-ons need access. These APIs will use browserSetting [1] to manage which extension has control over the pref. If it makes sense, the APIs will be added to the privacy namespace, but often that is not where they will belong, so we need somewhere else to put them.
These will differ from Chrome's contentSettings API [2] in that these prefs control the browser globally - they do not change settings on a site by site basis. Andy suggested the namespace `browserSettings`, which sounds good to me, so I am going to run with that unless anyone has a better idea.
[1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/privacy/BrowserSetting
[2] https://developer.chrome.com/extensions/contentSettings
Reporter | ||
Comment 1•8 years ago
|
||
Note that most of these are documented in https://docs.google.com/document/d/1HZiI-dqFATzLpmTtN1Bg6tD8y4N0Ne3D74LEWWgttOk/edit#
Comment 2•7 years ago
|
||
Will this allow WebExtensions to modify most prefs, or will this just have a small list?
In particular, will it allow WebExtensions to modify cookie prefs?
Flags: needinfo?(bob.silverberg)
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to quality+bugzilla from comment #2)
> Will this allow WebExtensions to modify most prefs, or will this just have a
> small list?
This is only about granting access to a specific set of prefs, so the latter.
>
> In particular, will it allow WebExtensions to modify cookie prefs?
Bug 1363860 will grant access to control cookie behaviour via a specific pref, but that's all that's planned for cookies at the moment. If there is something else you need, please open a separate bug for it, and feel free to make it block this bug.
Flags: needinfo?(bob.silverberg)
Comment 4•7 years ago
|
||
Without ability to get and set the following preferences, my Blend In extension loses most of its functionality if i convert it to WebExtension:
appversion.override
oscpu.override
platform.override
buildID.override
useragent.override
It will end up spoofing only HTTP User-Agent header (to say it's Windows, etc.), while all the navigator properties will be saying it's Linux, for instance.
Does this bug cover the above preferences, or should i open a new one?
P.S. I don't see the preferences in
https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/browserSettings
or elsewhere.
Comment 5•7 years ago
|
||
We consider each preference individually, so please file seperate bugs and making them block on this bug.
Updated•7 years ago
|
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•5 years ago
|
Priority: P2 → P3
Updated•5 years ago
|
Summary: [tracker] Implement WebExtensions API to give access to specific preferences → [meta] [tracker] Implement WebExtensions API to give access to specific preferences
Updated•5 years ago
|
Summary: [meta] [tracker] Implement WebExtensions API to give access to specific preferences → [meta] Implement WebExtensions API to give access to specific preferences
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•