1866005 - Social Media Trackers does not displayed under the blocked section, on the Protections panel

Status: NEW

(Core :: Privacy: Anti-Tracking, defect, P3)

Description

[Timea Zsoldos [:tzsoldos], Desktop QA]

Attachment: image.png

Found in

• Firefox 121.0b1

Affected versions

• Firefox 122.0a1
• Firefox 120.0

Tested platforms

• Affected platforms: Windows 10, macOS 13, Ubuntu 22

Preconditions

• Make sure that the "Custom" option is selected from the ETP section in about:preferences#privacy and select only the option "Cross-site tracking cookies, and isolate other cross-site cookies" in the Cookies section.

Steps to reproduce

1. Open Firefox browser with a new profile.
2. Go to https://senglehardt.com/test/trackingprotection/test_pages/social_tracking_protection.html
3. Click on the shield icon and observe the "Social Media Trackers".

Expected result

• The "Social Media Trackers" appears under the blocked section.

Actual result

• The "Social Media Trackers" not appears under the blocked section, see the issue in the attached image.

Regression range

• I will come back with regression range ASAP.

Additional notes

• If I interact with the ETP button by turning it "off" and then "on" again, the "Social Media Trackers" appears under the blocked section.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:zstimi, if you think that's a regression, could you try to find a regression range using for example mozregression?

Comment 2

[Oana Botisan, Desktop QA]

This is a n old regression. The best I could find was:

• last good build: 2019-11-02
• first bad build: 2019-11-03

On the build from 2019-11-03 for some reason the even after you turn ETP off and then on again, the Social Media Trackers are not displayed in the panel.

Comment 3

[Anca Soncutean, Desktop QA]

The expected behavior mentioned here is part of our automation effort. However, the bug is causing inconsistent test results, with the test passing for some and failing for others. It is still reproducible on my end (tested with the latest Beta and Nightly versions), and I have tried it on three different test machines (all running Windows).

Paul Zühlcke, do you have any insights on what might be causing this?

Comment 4

[Emma Zühlcke [:emz]]

This is not a UI bug. STATE_COOKIES_BLOCKED_SOCIALTRACKER does not get added to the content blocking log so the protections panel doesn't show the category. I'm not sure if the expected result is correct here though. If only cookie behavior 5 is enabled and all other ETP blocking is disabled, why would we show socialtrackers as blocked in the first place?

What's even weirder is that I'm setting these messages:

Request to access cookie or storage on “https://social-tracking-protection-facebook-digest256.dummytracker.org/cookie_access_test.html?test_origin=senglehardt.com” was blocked because it came from a tracker and content blocking is enabled.

Request to access cookie or storage on “https://social-tracking-protection-twitter-digest256.dummytracker.org/cookie_access_test.html?test_origin=senglehardt.com” was blocked because it came from a tracker and content blocking is enabled.

Request to access cookie or storage on “https://social-tracking-protection-linkedin-digest256.dummytracker.org/cookie_access_test.html?test_origin=senglehardt.com” was blocked because it came from a tracker and content blocking is enabled.

I don't think those should show up when ETP (storage/ cookie blocking) is disabled. Why are we still blocking cookies?

Comment 5

[Emma Zühlcke [:emz]]

Oh I see, the checkboxes in "Custom" are only for tracking protection. Social tracker cookie blocking is part of "Cookies". That means the tracker category should show up in the UI too in this configuration. It is logged in the console and the cookies seem to get blocked properly, but it doesn't show up because of the missing event / log. We need to find out why STATE_COOKIES_BLOCKED_SOCIALTRACKER isn't logged.

Comment 6

[Benjamin VanderSloot [:bvandersloot]]

I think it comes down to this logic. Basically we are seeing this as a third-party cookie that should be "blocked" (see partitioned) and are returning that as the reason to prevent it from showing up before we get to even testing if it is a social tracker. We also see a STATE_COOKIES_BLOCKED_TRACKER and STATE_COOKIES_LOADED for that host, so I imagine there is some confusion going on.

I also found the way blocks are attributed between protections in the panel a bit odd as social protections interact with 3pc blocking- so that could be a source of funniness with UI.