Closed Bug 1502361 Opened 7 years ago Closed 7 years ago

Remove Content Blocking toggle from about:privatebrowsing

Categories

(Firefox :: Protections UI, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
Firefox 65
Tracking Status
firefox65 --- verified

People

(Reporter: johannh, Assigned: johannh, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [privacy65])

Attachments

(1 file)

We are redoing the way content blocking is presented in product (with different "modes") and the toggle on about:privatebrowsing doesn't really fit anymore. It was always a bit misleading since we grouped TP under content blocking. The new minimum/standard setting will be having TP always-on in private browsing, and users who don't want it will need to opt out per-site by adding exceptions in the control center.
(In reply to Johann Hofmann [:johannh] from comment #0) > The new minimum/standard setting will be having TP always-on in private > browsing, and users who don't want it will need to opt out per-site by > adding exceptions in the control center. Do we need some copy for this? Or are we just removing the row with the icon and the toggle and leaving it at that?
Blocks: 1502374
(In reply to :Ehsan Akhgari from comment #1) > (In reply to Johann Hofmann [:johannh] from comment #0) > > The new minimum/standard setting will be having TP always-on in private > > browsing, and users who don't want it will need to opt out per-site by > > adding exceptions in the control center. > > Do we need some copy for this? Or are we just removing the row with the > icon and the toggle and leaving it at that? We should probably ask Bryan and Betsy what they had in mind for about:privatebrowsing. The AS team is currently working on a private search option for that page so the design might change significantly anyway. I also filed bug 1502374 to ensure that we offer users a way to restore their settings to default when they flipped the toggle to false in the past.
Flags: needinfo?(bbell)
Note: this line was added for the sake of about:privatebrowsing, and we may be able to remove it when this bug is fixed: https://searchfox.org/mozilla-central/rev/5b3b6b8fd9f90087f618c20382e631451136ed2b/toolkit/modules/AsyncPrefs.jsm#23
Blocks: 1501978
(In reply to :Ehsan Akhgari from comment #3) > Note: this line was added for the sake of about:privatebrowsing, and we may > be able to remove it when this bug is fixed: > https://searchfox.org/mozilla-central/rev/ > 5b3b6b8fd9f90087f618c20382e631451136ed2b/toolkit/modules/AsyncPrefs.jsm#23 Also https://searchfox.org/mozilla-central/rev/5b3b6b8fd9f90087f618c20382e631451136ed2b/toolkit/components/remotepagemanager/MessagePort.jsm#29
Assignee: nobody → jhofmann
Status: NEW → ASSIGNED
Priority: P2 → P1
This simply removes the content blocking section when TP is not enabled to avoid overpromising. We may update this UI to alert the user that TP is off after the UX team comes back with a new design.
Yup, thanks, had a small test failure on try, unfortunately. Will re-land now...
Flags: needinfo?(jhofmann)
Pushed by jhofmann@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/8bd9666a8a5b Remove Content Blocking toggle from about:privatebrowsing. r=Ehsan
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
I verified this issue on Nightly 65.0a1 (2018-11-07).
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: