Firefox not working on a lot of sites

[bjhansen53]

I have probably been using Firefox for 20 years and up until this past year I never had a problem. I am now constantly running across sites that I cannot access or do not work on Firefox. I wish I had kept a list because it would have been a long one. It has gotten to the point that I am considering using another browser for my default. I have tried getting this question answered several times and have gotten no response. If I do not get one soon, I will have to drop Firefox as my default browser. This is not a problem that I have had on just one computer, but on all 5 that I use.

[danmhi]

Please report any broken websites trough our reporting tool:
https://support.mozilla.org/en-US/kb/report-breakage-due-blocking

We're actively looking into these and figuring out mitigations.

In case you have ETP Strict turned on, be aware that certain elements on the websites might be unavailable because they are classified as trackers and we are blocking them. This is expected behavior in this mode.

[JimLongIsland]

I am having the same issue. I run Firefox 131.03 64 bit on Windows 11 and for awhile now have been having serious issues. When I try troubleshooting mode in Firefox the problems do not go away. As an example, today ,on the Washington Post site, most articles work but all political cartoons come up blank. Switch to Chrome and they work. On many sites clicking login buttons gets no response while in Chrome they work fine. This makes Firefox such a hit or miss that I have to switch my default browser.

[PonchT]

The employee that discusses "ETP" has provided accurate information. 
In order to resolve the issue and allow the applicable website(s) to load:

Go to Settings
Type Enhanced in the Search section (or go to Privacy and Security)
Select Manage Exceptions
Enter the address of the website(s) that are not loading/completing
Save Exceptions
Reload site(s)

Another option is to simply click the "Shield" (typically to the left of where you type the URL)

There have been  few websites where, oddly, if you click the shield again to re-enable the will then properly load.

[BruderKlaus_CH]

This doesn't work for me (Comp1  Ver. 134.0.1. Windows 11 and Comp2 Vers. 134.0.1. Windows 10). Under Win 11 it is completly impossible to run a video on YT. Comments are loaded, suggestions of other videos are loaded (just partially like with many FF versions before...not really working) ... no video is played. I have all security settings reduced to the lowest standard, I made an exception for YT (not blocking trackers etc.) ... doesn't work.  FF is becoming more and more unusable on some sites. Switching to Edge in those cases and it worked.
I am donating money to Mozilla, but it has become so problematic that it is frustrating. Perhaps Mozilla should focus on technology and proper software instead of politics? I will stop funding Mozilla until someone is addressing these problems...an official statement would be nice as a starter !!

[Anonymous]

I 100% agree.  I have used Firefox since the beginning, over 20 years.  Can't take it anymore.  Site upon site doesn't load.  Moved to Edge since I trust Google less than Microsoft.  Sad that the developers won't fix it.  If they use it like we do, how can they not see the same problems.

FYI,  I use Duck Duck Go for searches 90% of the time to avoid google.  It's pretty good now.

[danmhi]

Is this problem occurring when you use the latest version with a new profile (about:profiles)? Are any add-ons enabled?

[bogdanpsc]

On Firefox 136.0.2 after the security update I get these security.csp errors on many websites:

1. Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https: 'unsafe-inline' 'unsafe-eval'  

2. Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'none'”

Setting security.csp.truncate_blocked_uri_for_frame_navigations (in about:config) to false does not fix the problem

[freddyb]

Hi, my team is responsible for Content-Security-Policy (CSP). We haven't made any significant changes to CSP that I am aware of. But they might be related to an extension you are using. Could you disable the extension and try again? It might also just be that the page is having CSP errors that are logged to the console which are completely unrelated to why it is breaking. Many pages have that, actually. Especially when it's set to "report only".

If you want, you can also share the websites that are broken through https://support.mozilla.org/en-US/kb/report-breakage-due-blocking as @danmhi suggested. Websites that are not misbehaving for a lot of users will get more attention than those that are not widely reported.

[FrankTell]

Freddy, thanks for the update but, with all respect due, your "we did not change much so it's not our fault" answer is way too light. Fact is that numerous site no longer work since the last Firefox update and I^d appreciate if you could look into it more deeply. Two example: grok.com does not load and my bank prevents me from login in as JavaScript is apparently no longer activated (I checked about:config, and it is enabled). Chrome works fine with these two sites.
Thanks

[freddyb]

Hey, I totally understand your perspective Frank and I am happy to help. The thing is just that we get so very little information to make the bug reproducible on our end. We often times find web pages that break and fix them, but that only works if there's more actionable information. What we need is a bit more beyond the "example.com does not work", but exact steps you went through and what happened and what you expected to happen instead and the Firefox version number etc.

Asking these types of questions and handling every one of our hundres of millions of users doesn't work so well on an individual basis. That's why we have built the aforementioned tool to gather *all* the information we need. Please see https://support.mozilla.org/en-US/kb/report-breakage-due-blocking.

What I meant to say - and now realize may have not been explained in great enough detail - that I can rule out that the CSP errors in the console are due to a change in Firefox. That doesn't mean we don't want to help get the website working. It just means that the information is likely irrelevant or independent of the breakage. Unfortunately, what also happens often times is that web developers change their website in a way that does not adhere to best practices and universally applied web standards but rather according to some specific API that only works in some browser. This kind of breakage is easy for us to track, to a certain degree even fully automatically. And again - we are happy to help and really want the browser to work for everyone. But that requires a lot more information than just the site address. In this very specific example, grok.com works just fine for me. See screenshot attached. 

Thanks for pushing back and keeping us honest 🙂

[areles]

Many sites don't complete the login because they use reCAPTCHA. Forced to use MS Edge

[freddyb]

"Many sites" is unfortunately not enough information for us to proceed. We do know that reCaptcha works according to our tests, but it may behave differently on some pages. 

Can you please report all information required for us to help fix the issue by going through the steps at https://support.mozilla.org/en-US/kb/report-breakage-due-blocking? Thank you!