(From Bug 1042135 comment #0) > We currently have three options for DNT. > > The one saying that a user explicitly wants to be tracked seems to be > superfluous. Being tracked is (unfortunately) the standard on the web. Even > our SUMO page says that this option is effectively the same as not telling > the website about tracking preferences. By presenting more options to the > users here, we make it less likely for them to change the setting at all. > > We should therefore remove that option which would allow us to reduce the UI > to one simple checkbox: > > [ ] Tell websites that I do not want to be tracked > > The main reason for switching away from this design (bug 765398) seems to > have been the ad industry wanting the explicit opt-in. Two years later, I > don't think that's an issue anymore. Especially since we're the only browser > offering the "Do track" option. > > Sid, it looks like you've been very involved in this discussion. What's your > take on this? (From Bug 1081343 comment #0) > We want a new "Polaris" pref that can be enabled by users to opt-in to > privacy features/explorations that are still in an experimental stage. The > current plan is for this to be an ongoing program, with the first program > feature being Tracking Protection. > > Apparently the discussion on this resulted in the following requested > behavior: > > * The pref will only be in about:config. No UI for it yet. > * When the pref is enabled, it should enable the Tracking Protection pref > (privacy.trackingprotection.enabled) and expose the UI in bug 1031033 > * When the pref is disabled, it should disable > privacy.trackingprotection.enabled and hide the UI in bug 1031033 > * Similarly, enabling/disabling the Polaris pref should enable/disable DNT. > [Is this already being done by tracking protection?]

Except for the Polaris stuff, this will be fixed as soon as bug 1060852 attachment 8499098 [details] [diff] [review] checks in (which covers the DNT transition). Thus, unless you think that anything beyond that needs to be done (the enable-UI pref is browser only and therefore doesn't affect SeaMonkey), this is a duplicate.

Also, I have filed bug 1087529 for Thunderbird, which should be straight-forward to port as it's closer to the Firefox implementation than SeaMonkey's version. I'll get to that in parallel to updating the Help content for SeaMonkey in bug 1060852.

(In reply to rsx11m from comment #1) > Except for the Polaris stuff, this will be fixed as soon as bug 1060852 > attachment 8499098 [details] [diff] [review] checks in (which covers the DNT transition). So, duplicate or not?

Duping per feedback on IRC.