Tracking Protection page is only about Private Browsing

RESOLVED FIXED

Status

support.mozilla.org
Knowledge Base Content
P1
normal
RESOLVED FIXED
a month ago
18 days ago

People

(Reporter: francois, Assigned: Joni Savage ("need info" me))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a month ago
Currently Firefox links to this page from the tracking protection setting in about:preferences:

  https://support.mozilla.org/en-US/kb/tracking-protection-pbm?as=u&utm_source=inproduct

which is fine on release. On Nightly however, there is a pref to enable TP outside of Private Browsing as well. Also, starting in 57, we will be starting to expose that 3-level setting to users.

We also have this old unmaintained page on SUMO:

  https://support.mozilla.org/en-US/kb/tracking-protection-firefox

I can see two different approaches to supporting 57:

1. We update the tracking-protection-firefox page link to either tracking-protection-firefox or tracking-protection-pbm from the product depending on which UI is shown.

2. We merge the two SUMO pages and discuss both versions of the TP setting (either the tri-state radio buttons or the checkbox).
Flags: needinfo?(jsavage)
(Reporter)

Comment 1

21 days ago
Given that we are going ahead with the full tracking protection options (i.e. what used to be the Nightly UI) in 57 (see https://bugzilla.mozilla.org/show_bug.cgi?id=1393627#c5) and that we no longer have time to change the in-product links, we probably need to go with #2 and repurpose the tracking-protection-pbm page.
ran into francois in the vancouver office today, Firefox needs this i.e. comment 1 to be done for 57. Unfortunately, this decision was only made the morning of friday november 3rd, 2017, so i guess the right thing is to assign to you joni and setting to P1 to get it done quickly.
Assignee: nobody → jsavage
Status: NEW → ASSIGNED
Priority: -- → P1
(Assignee)

Comment 3

21 days ago
I've updated this article to reflect the three options in Nightly. I've also changed the title and fixed the redirect to expand the messaging to beyond Private Browsing.

https://support.mozilla.org/en-US/kb/tracking-protection
Flags: needinfo?(jsavage)
(Reporter)

Comment 4

21 days ago
Thanks Joni for the incredibly quick turn-around!
Status: ASSIGNED → RESOLVED
Last Resolved: 21 days ago
Resolution: --- → FIXED
(Reporter)

Comment 5

21 days ago
For reference, here's the change: https://support.mozilla.org/en-US/kb/tracking-protection/compare?locale=en-US&to=150388&from=148161
(Reporter)

Comment 6

21 days ago
It turns out Fennec also changed its tracking protection preferences in bug 1399014.

Joni, any chance we could get the Fennec SUMO page updated as well?

https://support.mozilla.org/en-US/kb/tracking-protection-firefox-android
Status: RESOLVED → REOPENED
Flags: needinfo?(jsavage)
Resolution: FIXED → ---
(Reporter)

Updated

21 days ago
See Also: → bug 1399014

Comment 7

20 days ago
(In reply to Joni Savage ("need info" me) from comment #3)
> I've updated this article to reflect the three options in Nightly. I've also
> changed the title and fixed the redirect to expand the messaging to beyond
> Private Browsing.
> 
> https://support.mozilla.org/en-US/kb/tracking-protection

Joni, I reverted your changes since your revision comment was " updated for 57" and you didn't post anything about this bug in the article discussion forum. I thought you had mixed up Nightly with Beta. 

Related discussion: https://support.mozilla.org/en-US/kb/tracking-protection/discuss/7289 [Fx58] Tracking Protection settings changed in Firefox 58 Nightly

Comment 8

20 days ago
I made a new revision that includes Joni's last update. See https://support.mozilla.org/en-US/kb/tracking-protection/history
(Assignee)

Comment 9

18 days ago
Sorry, Alice. I forgot to paste the bug info in my haste. 

François, I've updated the Android article as well. Thanks for flagging this.
Flags: needinfo?(jsavage)
(Reporter)

Comment 10

18 days ago
Thank you Alice and Joni!
Status: REOPENED → RESOLVED
Last Resolved: 21 days ago18 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.