[meta] Enable DoH in Fenix and Focus
Categories
(Fenix :: Browser Engine, enhancement, P5)
Tracking
(Not tracked)
People
(Reporter: cpeterson, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: meta, parity-chrome, Whiteboard: [fxdroid])
Bug 1591533 will add a new GeckoView API so apps can toggle and configure DoH. We don't have plans to enable DoH in Fenix or Focus at this time due to performance concerns.
If we choose to enable DoH in Fenix or Focus, we should probably enable it from the app code, not enabling it by default in GeckoView. Other GeckoView apps might not want to use the same DoH provider that Mozilla does.
Comment 2•1 year ago
|
||
Hi Chris, since Bug 1591533 just landed in Nightly, could we get someone assigned to this bug to add UI for DoH settings?
We likely want to mirror the choices in the DNS over HTTPS section of about:preferences#privacy -
- Default,
- Increased protection
- Max protection (I'm not a big fan of these two names 🙂)
- Off
Once users are able to configure their DoH settings we can experiment with turning on the feature in supported areas.
Reporter | ||
Comment 3•1 year ago
|
||
Hi Valentin, I'll add this bug to our Android backlog, but since it requires new UX design, we probably won't have bandwidth to work on this until 2024 Q1.
Updated•1 year ago
|
Reporter | ||
Comment 4•1 year ago
•
|
||
Valetin, IIRC, the Android team has worried that DoH will increase HTTP request latency and use more battery. We might want to run some performance tests to determine if there actually is any impact.
Also, I think some Android devices' system DNS providers use DoH. On those devices, we might want to offer another setting to use the system DoH provider. I think Chrome does this on desktop.
Comment 5•1 year ago
|
||
Valetin, IIRC, the Android team has worried that DoH will increase HTTP request latency and use more battery. We might want to run some performance tests to determine if there actually is any impact.
That worry stems from the fact that DoH connections have a longer timeout, which we can tweak on Android depending on the outcome of our tests.
Also, I think some Android devices' system DNS providers use DoH. On those devices, we might want to offer another setting to use the system DoH provider. I think Chrome does this on desktop.
We will probably add the capability to detect the platform's use of a secure resolver in bug 1852904 - which might help here.
Comment 7•1 year ago
|
||
If we are going to do an experiment with DoH on Android we will need to make sure we have all of the relevant Necko telemetry in Nightly. See bug 1854569.
Also note that bug 1591533 got backed out because it was resetting prefs for users that had set it. I think that needs to be fixed before we land it back.
Updated•10 months ago
|
Updated•24 days ago
|
Description
•