Expose HTTPS-Only preference in privacy.network
Categories
(WebExtensions :: General, enhancement, P1)
Tracking
(firefox84 fixed, firefox85 fixed)
People
(Reporter: ckerschb, Assigned: ckerschb)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
We would like to expose the preference (maybe read-only) so that extensions can observe if https-only is flipped on, in particular https-everywhere would like to know.
Maybe something similar to Bug 1593635 ?
Assignee | ||
Comment 1•3 years ago
|
||
Shane, could you provide some pointers on what the preferred way of exposing a preference is these days?
Assignee | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
I probably put this into privacy.network. browserSettings is generally more browser-feature related.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/privacy/network
I'm assuming it would be pretty simple, something like this (and you can pass readOnly: true
in the call to getSettingsAPI):
https://searchfox.org/mozilla-central/rev/1d34bd022de0b55c81d9db6026f69bda1d4a86d2/toolkit/components/extensions/parent/ext-privacy.js#75-82
https://searchfox.org/mozilla-central/rev/1d34bd022de0b55c81d9db6026f69bda1d4a86d2/toolkit/components/extensions/parent/ext-privacy.js#316-322
And you'd have to add to the schema.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 3•3 years ago
|
||
Pushed by csabou@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/eb0709aaa89d Expose HTTPS-Only preference to extensions within privacy.network. r=robwu,mixedpuppy
Comment 5•3 years ago
|
||
bugherder |
Assignee | ||
Comment 6•3 years ago
|
||
Comment on attachment 9189141 [details]
Bug 1678306: Expose HTTPS-Only preference to extensions within privacy.network.
Beta/Release Uplift Approval Request
- User impact if declined: Users of the famous and largely used extension
HTTPS-Everywhere
will be in some kind of limbo state if Firefox Users enableHTTPS-Only
Mode. Within this patch we expose a signal to extensions that allows to check ifHTTPS-Only
is enabled. Folks from the EFF (maintaners of https-everywhere) request if it's possible to uplift that so it's in FF 84. - Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): We are just exposing a
read-only
pref indicating ifHTTPS-Only
Mode is enabled. - String changes made/needed: no
Comment 7•3 years ago
|
||
Comment on attachment 9189141 [details]
Bug 1678306: Expose HTTPS-Only preference to extensions within privacy.network.
Makes the value of a couple prefs visible to extensions. No real user impact otherwise. Approved for 84.0rc1.
Comment 8•3 years ago
|
||
bugherder uplift |
Comment 9•2 years ago
|
||
Documentation updated in #1645 Adds httpsOnlyMode description to privacy.network page and confirmed that privacy isn't the subject of one of the web extension examples.
Updated•2 years ago
|
Description
•