>If this behavior gets adapted on more sites, we can expect even more users leaving Firefox
But I will just not go to the sites instead of using something other than Firefox.
121–130 of 191 posts
>If this behavior gets adapted on more sites, we can expect even more users leaving Firefox
But I will just not go to the sites instead of using something other than Firefox.
Earlier quoted context omitted.
But that's the issue. It's not my problem. My problem is maximizing the user experience for most of my users, and that involves squashing usability bugs common to all browsers and adding features that have been requested, not keeping up with the Gecko quirks-du-jour. (Speaking of "quirks-du-jour", the problem eventually "solved itself." The next major iteration of Firefox fixed a rendering regression and resolved the…
So a tragedy of the commons? See it is your problem to offer something to the general public then serve only the defacto monopolist instead of web standards. Because with each small compromise we each contribute to the problem until it reaches a breaking point. All the while those on the margins suffer, some with no real alternative. For ex in poorer areas where they cannot afford a computer that runs Chrome (which h…
Earlier quoted context omitted.
Quoted post unavailable.
Why jump to attacking them? Occam's razor applies, and there's no proof Cloudflare explicitly is targeting Firefox specifically, unless you somehow have internal access to their source and know there's checks explicitly looking for FF there.
Earlier quoted context omitted.
Really? I'm a firefox user too and whilst I occasionally bump into some situation as you describe where I need to hop onto Chrome, I genuinely can't remember the last time this happened. Nope, actually - sometime last year, with some poorly-coded gig ticket purchase thing, if I remember right. I was able to check the code and amend some stupid niggle in WebDev tools to get around it. Not saying I should have to accep…
For a while now I can't even access WhatsApp Web [1] through Firefox. It gets stuck on the loading page and keeps refreshing itself forever. I have to resort to Chrome whenever I need WhatsApp on my laptop. [1] https://web.whatsapp.com
Looks like there are already a couple bug reports about whatsapp.com, but not the forever-refreshing page you see:
https://webcompat.com/issues?page=1&per_page=50&state=open&s...
I use Firefox Focus on my phone (opens links from apps in a private session - generally a great idea!) and always get this 5 second delay (which is often actually 10 or more seconds). I never considered that it's a Firefox-only thing!
Earlier quoted context omitted.
Why jump to attacking them? Occam's razor applies, and there's no proof Cloudflare explicitly is targeting Firefox specifically, unless you somehow have internal access to their source and know there's checks explicitly looking for FF there.
I think you mean Hanlon's razor, but that adage is a farce. Every scoundrel in the world knows the trick of pretending it was all a mistake. Skepticism is warranted.
(There's a reason Hanlon's razor was given that name, I'm pretty sure, and that's because it's not too dissimilar from – essentially it's a much-more-situation-specific subset or variant of – Occam's razor. But I don't think "attribute to stupidity" was what the parent comment was suggesting.)
Earlier quoted context omitted.
I've used Firefox and Mozilla for what, 20 years? And I've never bumped into a situation like this. Some very clearly shit internal IT systems had pathetic IE requirements, but never one that said sorry go get chrome
They don't always say "go get chrome" but one example that still happens to me is logging in to Outlook email at work, if I use Firefox I get a hobbled "basic HTML" interface, if I masquerade as Chrome on Windows I get the full UI and it all works perfectly. Google drive is another one, where some things stop working depending on the user agent I'm presenting.
UA sniffing is soooo 2008.
Earlier quoted context omitted.
Why jump to attacking them? Occam's razor applies, and there's no proof Cloudflare explicitly is targeting Firefox specifically, unless you somehow have internal access to their source and know there's checks explicitly looking for FF there.
It's pretty simple to check. Go to https://www.g2.com/ in various browsers. That's what I did when I read the article. Here are my results: Firefox: Javascript challenge Chromium: No javascript challenge Edge: No javascript challenge How could you call this anything but an attack against firefox? edit: Seems cloudflare has responded[1] and they claim it is a setting set up by the site author. So this attack is done b…
edit: with FF OFC.
I mean, with that market share, popularity among open source fans... it's an easy group to target and filter oddballs. I'm a Firefox user and I'm used to this treatment at every step of the way, no matter if it's about software, airports, opening a bank account so I can receive a salary, etc. Fundamental things everyone wants to do are being made hard to do the right way. It's always anti privacy, anti self repair, a…
Really? I'm a firefox user too and whilst I occasionally bump into some situation as you describe where I need to hop onto Chrome, I genuinely can't remember the last time this happened. Nope, actually - sometime last year, with some poorly-coded gig ticket purchase thing, if I remember right. I was able to check the code and amend some stupid niggle in WebDev tools to get around it. Not saying I should have to accep…