[ux] Design perferences screen for enabling/disabling tracking protection and DNT

RESOLVED FIXED

Status

()

Firefox
General
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: madhava, Assigned: phlsa)

Tracking

unspecified
x86
Mac OS X
Points:
5
Bug Flags:
firefox-backlog +
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ux])

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

3 years ago
When opting in to tracking protection, a user should be able to choose a blocklist provider, when there are multiple options.

People opt into tracking protection in Preferences, so this choice should probably be made there.

Updated

3 years ago
Flags: qe-verify-
Flags: firefox-backlog+
Whiteboard: [ux]

Updated

3 years ago
Points: --- → 5

Updated

3 years ago
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Iteration: --- → 35.1
Expanding the scope of this bug to include the general design of the switch. The point value can stay the same.
Summary: [ux] Allow users a choice of tracking protection list providers → [ux] Design perferences screen for enabling/disabling tracking protection and DNT
Created attachment 8489888 [details]
Wireframe for Tracking Protection Preferences

Wireframe attached.
This has been discussed with Chad and Madhava.
The strings are still subject to some debate, but the structure stands.

Styling-wise, we can use the controls we currently have in In-Content-Preferences.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Created attachment 8496610 [details]
Wireframe for Tracking Protection Preferences

I updated the mockup based on feedback from mmc and mconnor:

1. Added ability to remove sites from the personal whitelist

2. Removed the functionality to add custom blocklists. These lists are way more complicated and require in-depth knowledge to manage effectively. Therefore it doesn't make sense to expose anything beyond disabling/enabling lists in the UI.
Attachment #8489888 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.