1287952 - Feature rqst: Same behavior for third-party content as for cookies in Firefox

Status: UNCONFIRMED

(Core :: General, enhancement)

Description

[Sid]

User Agent: Mozilla/5.0 (Linux; rv:35) Gecko
Build ID: 20160623154057

Steps to reproduce:

May I suggest a new function for Firefox related to dealing with third-party content (e.g. images, fonts, AV, iframes, etc.) on web-pages like with the cookies. So the users would may select:
- allow third-party content (no restriction);
- disallow third-party content (full restriction, only the same origin content allowed);
- allow only sub-domain third-party content (e.g. subdomain.domain.com content allowed for webpage from domain.com);
- allow all same domain sub-domains third party content (e.g. subdomain2.domain.com content allowed for webpage from subdomain1.domain.com).

Comment 1

[:Gijs (he/him)]

This would break large portions of the web (notably most sites that rely on non-same-domain CDNs for images or scripts, which is likely to be almost everything in the alexa top 500). So I'm not convinced it makes sense to implement this. In any case, the implementation would have to live in Gecko/Core, so moving this there.

Comment 2

[Sid]

(In reply to :Gijs Kruitbosch from comment #1)
Thanks for moving topic to the right section.

As for breaking the web by the proposed feature, the solution is in the user-definable whitelist for CDNs, etc.

But in general I'm against the whole approach that some improvement in user control over the downloadable content may break something within users control, e.g. whole web. Lets allow website designers to do what they want, e.g. use CDNs, third-party trackers, ad scripts, etc. Its their choise and soverign right to what they want. But on the other hand, the users soverign right is to download what they want, not what the site designers want.

Would I, as a user, get some sites inoperative? OK, it's my decision to choose such settings for third-party content and my problem, I would deal with it. Just let me decide and be the first who implement it in the browser. While the Mozilla Team works for users, not for website designers, I hope they would hear our voice.

Comment 3

[Simon Mainey]

Hannah, another dead privacy keyword ticket? Since network partitioning and now TCP (rolling out by default), I see no reason for blocking third party content (which users can do with a content blocker extension such as uBlock Origin)

Comment 4

[Paul Zühlcke [:pbz]]

Please don't needinfo folks digging up old bugs that need triage. We have bug triage owners that can go through these bugs and decide what to do with them.