Closed Bug 1510734 Opened 11 months ago Closed 11 months ago

Need to update about:preferences for Content Blocking = Strict

Categories

(Firefox :: Preferences, defect, P1)

defect

Tracking

()

VERIFIED FIXED
Firefox 65
Tracking Status
firefox65 --- verified

People

(Reporter: mheubusch, Assigned: ewright)

Details

(Whiteboard: [privacy65])

Attachments

(2 files)

The label for the cookie setting for the Content Blocking = Strict setting should change from All third-party cookies to  Third-party tracking cookies
Priority: -- → P2
Whiteboard: [privacy65]
Assignee: nobody → ewright
Status: NEW → ASSIGNED
The strict category should block third-party tracking cookies instead of all third-party cookies. This changes the requirements to match that category, so existing strict users will be moved to custom.
Priority: P2 → P1
Pushed by ewright@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a5acc2768905
Content Blocking strict setting now uses network.cookie.cookieBehavior=4. r=johannh,flod
Thanks, on it. I must've run that test on an incorrect branch or something... my bad.
Flags: needinfo?(ewright)
Pushed by ewright@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1de763410269
Content Blocking strict setting now uses network.cookie.cookieBehavior=4. r=johannh,flod
https://hg.mozilla.org/mozilla-central/rev/1de763410269
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 65
I can see the wrong string in firefox nightly 65.0a1 (2018-11-28) (64-bit) in Linux x86_64

I can verify that this is fixed in latest beta 65.0b6 (64-bit)  

Build ID 	20181220174318
User Agent 	Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0
QA Whiteboard: [testday-20181221]
I have reproduced this bug with Nightly 65.0a1 (2018-11-28) on Windows 10, 64 Bit ! 

This bug's fix is Verified with latest Beta !

Build   ID    20181220174318
User Agent    Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

[testday-20181221]
As per comment 7 and comment 8, this is verified as fixed in both linux and windows. Marking this accordingly.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.