[tracker] Implement WebExtensions API to give access to specific preferences

NEW
Unassigned

Status

P2
normal
a year ago
2 months ago

People

(Reporter: bsilverberg, Unassigned)

Tracking

(Depends on: 4 bugs, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: triaged)

(Reporter)

Description

a year ago
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)

Updated

a year ago
Depends on: 1339550
(Reporter)

Updated

a year ago
Depends on: 1363859
(Reporter)

Updated

a year ago
Depends on: 1363860
(Reporter)

Updated

a year ago
Depends on: 1364929
(Reporter)

Updated

a year ago
Depends on: 1364931
(Reporter)

Updated

a year ago
Depends on: 1364936
(Reporter)

Updated

a year ago
Depends on: 1364942
(Reporter)

Updated

a year ago
Depends on: 1364971
(Reporter)

Updated

a year ago
Depends on: 1364972
(Reporter)

Updated

a year ago
Depends on: 1364975
Depends on: 1368507

Comment 2

a year 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

a year 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)
(Reporter)

Updated

a year ago
Depends on: 1362787
Depends on: 1313939
(Reporter)

Updated

a year ago
Depends on: 1361364

Updated

a year ago
Depends on: 1376394

Updated

a year ago
Depends on: 1322308
Depends on: 1379560
No longer depends on: 1313939

Updated

a year ago
Depends on: 1374188

Updated

a year ago
Depends on: 1391501

Updated

11 months ago
Keywords: meta
(Reporter)

Updated

11 months ago
Depends on: 1400805

Comment 4

10 months 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

10 months ago
We consider each preference individually, so please file seperate bugs and making them block on this bug.

Updated

10 months ago
Depends on: 1414078

Updated

10 months ago
Depends on: 1414079

Updated

10 months ago
Depends on: 1414080

Updated

10 months ago
Blocks: 1414081

Updated

10 months ago
No longer blocks: 1414081
Depends on: 1414081

Updated

10 months ago
Depends on: 1414489

Updated

10 months ago
No longer depends on: 1414489
Depends on: 1417810

Updated

7 months ago
Depends on: 1427071

Updated

2 months ago
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.