Connection dialog says DoH is not enabled, when it is enabled via Remote Settings
Categories
(Firefox :: Settings UI, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox89 | --- | unaffected |
firefox90 | --- | verified |
firefox91 | --- | fixed |
People
(Reporter: nhnt11, Assigned: nhnt11)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-release+
|
Details | Review |
Missed this in bug 1713036.
In the Connection dialog, we should use DoHConfigController.currentConfig.enabled instead of doh-rollout.enabled
Assignee | ||
Comment 1•4 years ago
|
||
[Tracking Requested - why for this release]:
This is a bug :-)
We should make sure this is fixed in 91.
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Assignee | ||
Comment 3•4 years ago
|
||
In bug 1713036, I modified the DoH preferences code to look at DoHConfigController.currentConfig for state. This will get us the values actually in use, sourced from prefs + Remote Settings. I missed changing over this one pref to that new system.
Comment 4•4 years ago
|
||
(In reply to Nihanth Subramanya [:nhnt11] from comment #1)
[Tracking Requested - why for this release]:
This is a bug :-)
We should make sure this is fixed in 91.
It'd be pretty useful to understand how this impacts users and/or usage/rollout of DoH.
Assignee | ||
Comment 5•4 years ago
|
||
(In reply to :Gijs (he/him) from comment #4)
(In reply to Nihanth Subramanya [:nhnt11] from comment #1)
[Tracking Requested - why for this release]:
This is a bug :-)
We should make sure this is fixed in 91.It'd be pretty useful to understand how this impacts users and/or usage/rollout of DoH.
Users in the rollout would see that DoH is not enabled when viewing their connection settings, and may try to enable it manually which will unenroll them from the rollout. However, they'll still have DoH, just without heuristics.
Generally the fact that heuristics aren't really exposed in the UI is a larger issue that product is working on for H2.
Comment 7•4 years ago
|
||
bugherder |
Comment 8•4 years ago
|
||
Set release status flags based on info from the regressing bug 1713036
Updated•4 years ago
|
Assignee | ||
Comment 9•4 years ago
|
||
Comment on attachment 9228834 [details]
Bug 1718097 - Use DoHConfigController.currentConfig.enabled instead of doh-rollout.enabled in about:preferences. r=#preferences-reviewers!
Beta/Release Uplift Approval Request
- User impact if declined: This uplift is in support of unblocking our rollout of DoH in Canada. The patches for which uplift is being requested update the DoH settings UI to work better with Remote Settings, and simplify the Normandy recipe for the rollout.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1713036, Bug 1720379, Bug 1718097, Bug 1719851, Bug 1714486
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky): The changes have been baking for a while and work well. Medium risk because of the number of patches we need to uplift.
- String changes made/needed:
Comment 10•4 years ago
|
||
- We verified this issue across platforms (Windows 10 x64, Ubuntu 20 x64, macOS 11.4) using the 90.0.2 try-build provided by Nihanth.
- We performed smoke testing using the Remote Settings Stage environment on the DoH Preferences UI and didn't encounter any issues.
- After enrolling in the Canada experiment, we verified that the CIRA (Canadian DNS provider) was already enabled by default.
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Comment on attachment 9228834 [details]
Bug 1718097 - Use DoHConfigController.currentConfig.enabled instead of doh-rollout.enabled in about:preferences. r=#preferences-reviewers!
approved for 90.0.2
Comment 12•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Description
•