Open Bug 1868151 Opened 2 years ago Updated 2 years ago

ETP custom settings don't support controlling every setting ETP strict enables

Categories

(Firefox :: Settings UI, defect, P3)

defect

Tracking

()

People

(Reporter: emz, Unassigned)

Details

Attachments

(1 file)

The ETP settings under about:preferences#privacy allow the user to switch between "Standard", "Strict" and "Custom". While "Standard" and "Strict" are presets, "Custom" allows users to have more granular control over anti-tracking related settings.

However the "Strict" preset controls many features that "Custom" does not expose. This is bad in terms of UX, users can't get maximum privacy via "Custom" mode.

It also leads to unexpected, non-obvious behavior where settings are applied differently depending on the order of category selection:
If a user switches from "Standard" directly to "Custom", even if they adjust all the settings there, they won't get maximium protection, since the "Strict" preset is not applied. In order to get "Strict" prefs + "Custom" they need to first switch from "Standard" to "Strict" and then to "Custom".

Attached video 1868151.m4v

Here is an example showing how query stripping gets enabled when switching from "standard" -> "strict" -> "custom", but not enabled for "standard" -> "custom"

Do you know specifically what other settings in addition to query stripping also have this problem? I'm imagining it might be a bit of a pain to identify those.

Severity: -- → S3
Flags: needinfo?(pbz)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: