Count me in as well. I only use Google Chrome for Google meet calls, as some feature are not working on Firefox (I'm sure this has nothing to do with the fact that Google makes both chrome and meet ;)
Does it work in Ungoogled Chromium? I use that just on principle when nothing else works (which, in agreement with the previous posts, is rarer for me than people seem to claim)
You can report websites that don’t work in Firefox on webcompat.com and Mozilla web developers will test and diagnose the problem. When possible, they attempt to reach web developers at the site (using personal contacts or referrals when official channels aren’t working) to share the bug report and a suggested fix.
In other cases, Firefox can include a site intervention script to patch the site or send a different browser User-Agent string to make it work.
Have you tried either in an incognito/private browsing session? If it works there then it could point to needing a cache/cookie clear. If not then the issue may lie outside your box (try a vpn?)
A couple of things have helped me solve issues when trying to load sites in Firefox that will work in Chrome/Vivaldi, etc.:
1.) Refresh Firefox: Click the menu button with 3 lines -> "Help" -> "More troubleshooting information" -> "Refresh Firefox..."
2.) Check your Enhanced Tracking Protection settings from the Privacy & Security tab in the Settings menu. If it's set higher than Standard, it could be causing sites like reddit, sites that use Cloudflare for protection, etc., to load incorrectly or fail to load entirely.
Not my experience at all. Firefox works great for all the popular sites and 99+% of the unpopular ones. The trouble comes with websites that generally seem shoddy. I haven't had to install and delete Chrome for a long time!
Same. Actually I've had it the other way around a few times, when a site doesn't work in Chrome but works in Firefox. Perhaps though it was some caching issue because it worked OK in Chrome's Incognito mode. However, it was easier to just fire up Firefox than diagnose/debug Chrome.
In many many years of Firefox use, it has always loaded my sites with perhaps only one exception, but that was an odd graphics css treatment the signed out Patreon homepage used, probably fixed by now.
> I would love to use this as my daily driver, but a lot of popular sites don't even work with Firefox.
you mean minor aesthetics differences or functionality? I just use firefox, I don't even have chrome, and everything works. And I use mainstream web, nothing too niche.
small group of lazy front-end people? i think you actually mean a small group of chrome developers single-handedly deciding how web should work, while having the vast majority of the market share to push those decisions.
Well, no, that is not how it works. Blink undoubtedly has an oversize influence on 'web standards' (which are more and more defined as 'whatever Blink does') but that would not be that much of a problem if web developers built and tested their sites against more than just Chrome and Edge (Blink) and Safari (Webkit). History is repeating itself since the same thing happened when Microsoft's Internet Explo[rd]er was the dominant browser and developers only tested against that, putting a 'Best viewed using Internet Explorer' badge on their sites.
i am aware, i work as webdev and my current project is only Blink compatible. my employer does not want me to waste any time ensuring i support other browsers that are not going to be used.
web should be able to be viewed in any browser and get the same document.
I'm not particularly experienced with web browsers, but whenever I hear people who know what they're talking about, I always leave convinced that this is exactly the problem.
If there are sites that work on Chrome but not Firefox, it just seems to me that either:
- Chrome or Firefox must be breaking web standards
- Web standards must be unspecified for that use case
I have no idea the fix though, the web is so massively complex now, that I don't even know what specifying standards for every use case would involve.
Most web standards are codifying existing functionality, not the other way around.
Chrome/Blink has exclusive APIs, that often are not on track to be a standard.
This makes Safari (Webkit) and Firefox (Gecko) look bad, because they end up having to implement the same APIs, and then, maybe, it's standardized. Browser extension APIs come to mind.
I wish the situation was more neat and tidy, but it's not.
As a web developer, the things that bother me the most are the small differences in edge cases between the rendering engines.
What happens when you put a percentage height on a row in a table. What happens when an element has a margin that doesn’t fit in its parent. How does adding display: flex effect how text is laid out inside an element.
These are things that Gecko and WebKit/Blink handle differently. Some of them are defined in the spec and have tracking bugs, but some of them just aren’t addressed. I don’t think it’s maliciousness or laziness on anyone’s part, but the web is too complicated for there to be multiple perfectly compatible rendering engines.
I exclusively use Firefox, and I probably browse more websites than most. I very rarely run into websites that don't work on Firefox, and I can't recall the last time I ran into a page that didn't work on Firefox when serving a Chrome UserAgent (btw, if you're a web developer and you're accessing your user's UA, you're doing something horribly wrong. Stop).
Which sites don't work with Firefox? I'm a daily Firefox user for 15 years now and I can count on a few fingers the amount of sites that were "broken" in FF (and weren't a legacy IE issue).
Are you sure they are lazy? Maybe they are overworked, exhausted and constantly pressured by management to output new features? Did you ever work as a front end developer?
I hate what a small group of lazy front-end people have done to our world...