Partitioned cookie or storage access message is not triggered in WebConsole for edition.cnn.com
Categories
(DevTools :: Console, defect, P3)
Tracking
(firefox81 affected)
Tracking | Status | |
---|---|---|
firefox81 | --- | affected |
People
(Reporter: cbadau, Unassigned)
References
Details
Affected versions
- Firefox 81 Beta 5 (buildID: 20200901203141)
Affected platforms
- Windows 10
- Ubuntu 18.04
Steps to reproduce
- Launch Firefox.
- Set network.cookie.cookieBehavior = 5, privacy.partition.network_state= true and urlclassifier.trackingAnnotationTable.testEntries = known-tracker.englehardt-tracker.com. Restart the browser.
- Navigate to any website that has lots of trackers, e.g. https://edition.cnn.com/.
- Open the Web Console.
- Observe the log console displayed for the storage access blocked.
Expected result
- The following message is displayed in the Web Console, for the partitioned storage:
"Partitioned cookie or storage access was provided to “<URL>” because it is loaded in the third-party context and storage partitioning is enabled."
Actual result
- The message is not displayed in the Web Console.
Regression range
- I will check if this is a regression ASAP.
Suggested severity
- S3
Comment 1•4 years ago
|
||
Thanks for the report.
I don't see the message either (tested on Win10 + the current Nightly)
Nicolas, can you please take a look at this, thanks!
Honza
Comment 2•4 years ago
|
||
Camelia, any luck with the regression range?
Honza
Comment 3•4 years ago
|
||
I think it's because the default cookie behavior of the beta channel is 4(ETP) instead of 5(dFPI). The message 'Partitioned cookie or storage access was ...' is for dFPI. So, it's expected to not see it in beta.
Reporter | ||
Comment 4•4 years ago
|
||
I've retested today on Firefox 81 Beta 7 and on latest Nightly 82.0a1 (2020-09-06) using https://www.officedepot.com/ and the message is correctly displayed in the Web Console for this website.
Is it possible that https://edition.cnn.com/ does not have cookies that need to be isolated or blocked?
Reporter | ||
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Oh, I missed that you have changed the cookiebehavior to 5 when did the test.
In my nightly 82.0a1 (2020-09-06), I don't see the message for https://edition.cnn.com/. But I can see it using https://www.officedepot.com/. Same for the Firefox 81 beta 7 with cookie behavior 5.
So, I think it's possible that https://edition.cnn.com/ doesn't load any non-tracker third-party context.
Reporter | ||
Comment 6•4 years ago
|
||
It seems that https://edition.cnn.com/ doesn't load any non-tracker third-party context (as Tim said in previous comment). For now I think there is no need for regression range, because using https://www.officedepot.com/ everything correctly works.
Comment 7•4 years ago
|
||
(In reply to Camelia Badau [:cbadau], Release Desktop QA from comment #6)
It seems that https://edition.cnn.com/ doesn't load any non-tracker third-party context (as Tim said in previous comment). For now I think there is no need for regression range, because using https://www.officedepot.com/ everything correctly works.
Does that mean we can close this bug Camelia?
Reporter | ||
Comment 8•4 years ago
|
||
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #7)
(In reply to Camelia Badau [:cbadau], Release Desktop QA from comment #6)
It seems that https://edition.cnn.com/ doesn't load any non-tracker third-party context (as Tim said in previous comment). For now I think there is no need for regression range, because using https://www.officedepot.com/ everything correctly works.
Does that mean we can close this bug Camelia?
Yes, I think we can close this bug.
Description
•