[jjoonathan]

Is it just me or has the web's compatibility with Firefox taken a nosedive recently? It used to just be my employer's HR software that was chrome-only, but in the last year my power utility website, apartment complex website, and even major websites like https://www.deviantart.com/ (which I was trying to visit just 10 minutes ago) have broken in Firefox but not chrome. Badly, too. These aren't "the layout is different in FF and nobody noticed" bugs, they're "site infinitely redirects" bugs or "login button doesn't submit" bugs.

Debug steps: turn off bitwarden, my only extension. Never helps. Ctrl+Shift+Del cookies. Never helps. Sigh, open chrome. Works first time.

Is it just me or did the web up and dump firefox just when it started to get good?

:(

[JoshuaDavid]

I've noticed some of this lately - in a significant fraction of cases, it comes from Firefox honoring X-FRAME- OPTIONS while chrome ignores them, so e.g. payments work on chrome on sites that don't work on FF.

[ornornor]

At my current employer, the web apps are only ever tested on chrome. If it works on chrome, it ships. I think I’m the only one using Firefox and making sure it works there before chrome.

[jjoonathan]

Thanks for fighting the good fight.

[zo1]

We recently had some "FE devs" make a spiffy new SPA for some internal product. When I got to testing it on Firefox cause that's my main browser, I got a blank white page.

I asked them and they're like "yeah, it only works on chrome-based browsers". Or something to that effect. It's not like some CSS was wonky, or a bug somewhere... No, the default process of them building the SPA somehow yielded a completely non-functioning app for Firefox.

[lemax]

Services with absent engineers should be breaking left and right this month due to changes to SameSite attributes on cookies that hit browsers in early Feb. The intention of the change is to provide some long overdue changes to defaults on cookies with better privacy.

This is a change that’s been underway for years but came as a surprise when it actually shipped. I coordinated updates to ~40 packages owned by 5 different teams at my company, and had to put aside a good amount of other critical product work for about a week to ensure we didn’t encounter any customer issues.

The crux of the issue for maintainers is that Auth flows that require cookies to be sent around different origins (e.g. OAuth with form_post) will no longer work unless they update the cookies to explicitly be SameSite=none and Secure=true. Chrome led the pack on shipping the changes to browsers, but also implemented a special timeout rule that temporarily allows cookies that don’t meet the new spec to be set anyway to try to ensure auth flows don’t break. Eventually they will lift this timeout. Firefox has shipped support but has not implemented such a timeout.

[bootsbootsboots]

At one place i was at, people were completely aware but firefox issues were always deprioritized because the analytics showed low percentage of users affected. I wouldnt be surprised if a higher proportion of users with firefox also have adblock which further skew these usage stats

[chrisweekly]

I've unexpectedly had precisely the opposite experience; as of recent changes to cookie handling and 3rd party content in Chrome, several sites / webapps have either stopped working at all in chrome, or have serious issues -- while rendering and performing just fine in FF.

[1_player]

Some tech demo sites are Chrome only but I’ve yet to encounter a broken site on Firefox. The only issues I have are mostly due to adblock or my Pi Hole. I haven’t used Chrome in years.

[laktak]

Have you tried turning off ublock/etc. first?

For me it's usually extensions.

[kubanczyk]

Consider submitting a bug ticket. You are the customer after all.