Closed Bug 1492585 Opened 3 years ago Closed 3 years ago
Switch "All Detected Trackers" to "Tracking Protection" if Fastblock UI is not exposed
I spoke with UX, copy, frontend, and Product. If browser.contentblocking.fastblock.ui.enabled" is false (i.e. fastblock UI not exposed in preferences), replace the "All Detected Trackers" string with with "Tracking Protection". Luckily, both strings are in product already.
This will cause us to show [Tracking Protection Blocked/Add Blocking] in the Control Centre. That doesn't sound right...
(In reply to :Ehsan Akhgari from comment #1) > This will cause us to show [Tracking Protection Blocked/Add Blocking] > in the Control Centre. That doesn't sound right... oh... yes. Michelle/Bryan - any other ideas?
Then let's call it "Trackers" which will make sense as a thing we block.
Unfortunately we don't have "Trackers" in our existing strings, so we would need to ask if it's okay to uplift.
Adding new strings now is a problem: the deadline for l10n is Oct 9. That's 2.5 weeks, assuming we land the string changes today. The risk is to ship localized versions with that string in English. As long as you are aware of that risk, we can uplift strings, but I would honestly prefer avoid doing that.
WONTFIXing based on comment 5 and after checking with Michelle.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.