[unwabuisi]

As a Web Dev I am split on a movement like this. I understand the need for users to control what data they allow companies to have on them, but if other browsers do not follow suit, what will that mean for deployment and making sites consistent across browsers? If Firefox is blocking popular libraries or scripts that end up breaking some webpages the user experience still suffers

[wfleming]

I think that's effectively already the world we live in. As a uBlock user I occasionally run into sites that are broken because they wrote code assuming that some function provided by an analytics library would exist, and it doesn't because that library got blocked. I file bug reports when I can, and I'm concientous about handling these cases in my own code.

Writing code to handle the failure to load of third party scripts like this should really be a best practice anyway. Even if you use subresource integrity checks on all the external scripts you load, what if some analytics provider's site is down for a while? Do you want your site to still work? I do. (Obviously this does not apply to scripts that are actually necessary for the core functionality of your site, but that doesn't really apply to analytics/tracking tools for the most part.)

Making this the default behavior of FF will make this sort of breakage more visible to more people, it's true. If anything maybe this will encourage sites to write their code to handle failure more elegantly and I'll spend less time annoyed. One can dream.

[hegz]

Site owners were given freedom for a long time and they consistently chose to do the wrong things with no sign of ever stopping. Now browsers have to step in and moderate them.