Open Bug 1627322 (tp-facebook) Opened 4 years ago Updated 1 month ago

[meta] Tracking Protection breaks sites relying on Facebook resources

Categories

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

Product:
Core
Component:
Privacy: Anti-Tracking
Type:
defect

Tracking

()

People

(Reporter: twisniewski, Unassigned)

References

(Depends on 29 open bugs, Blocks 3 open bugs)

Details

(Keywords: meta)

This is a meta-bug for cases where tracking protection is breaking Facebook comments from loading on third-party sites.

Depends on: 1627171
Depends on: 1620955
Depends on: 1485639
Depends on: 1492100
Depends on: 1545259
Depends on: 1609354
Depends on: 1485372
Priority: -- → P3
Depends on: 1630546
Depends on: 1609867

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3

If embedded Facebok contents require cookies from facebook.com (third party cookie) to embed contents, this is the right behavior.

No longer depends on: 1627171
No longer depends on: 1620955
No longer depends on: 1609354
No longer depends on: 1545259
Alias: tp-comments-facebook → tp-facebook
Depends on: 1687474
Depends on: 1687476
Depends on: 1687470
Depends on: 1694138
Depends on: 1698840
Depends on: 1702961
Depends on: 1705336
Depends on: 1702767
Depends on: 1634028
Depends on: 1698021
Depends on: 1695925
Depends on: 1265457
Depends on: 1675019

This bug has many depending bugs related to specific sites.
However, they are about the common problem of "Facebook contents on each site not working with 3rd party cookies blocked".

I think we should not file tons of site-specific bugs with the same cause.

The problem is that the cause in Strict mode is that the Facebook SDK is being blocked, not due to cookies being blocked. Shimming it requires having a list of sites to test it, and I prefer closing them as we come up with shims or other fixes, since these kinds of issues may not all use precisely the same APIs/libraries/etc, and may require multiple fixes.

If it bothers us to leave them all open or have separate bugs, we could duplicate them to this bug, but that also strikes me as suboptimal (as it increases the risk that we might miss sites thinking they are fixed/tested already).

Depends on: 1708174
Depends on: 1722243
Blocks: tp-breakage
Depends on: 1746055
Depends on: 1735311

The severity field for this bug is relatively low, S3. However, the bug has 4 duplicates.
:timhuang, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(tihuang)
Flags: needinfo?(tihuang)
Keywords: meta
Summary: Facebook comments not loading with tracking protection → [meta] Facebook comments not loading with tracking protection
Depends on: 1761715
Depends on: 1770327
Depends on: 1772491
Depends on: 1723735
Depends on: 1776163
Depends on: 1787698
Depends on: 1787150
Depends on: 1786014
Depends on: 1784214
Depends on: 1790622
Summary: [meta] Facebook comments not loading with tracking protection → [meta] Tracking Protection breaks sites relying on Facebook resources
Depends on: 1797071
Depends on: 1818698
Blocks: 1885298
You need to log in before you can comment on or make changes to this bug.