Everything worked perfectly as it always does.
firefox has a lot of bugs with our store
Well, I think you got that backwards.
Firefox has a “bug” that makes our tracking code not work. Please switch to Chrome so we can track you.
I use my separate pr0n browser for this kind of sites. It’s set up to completely reset every time.
That doesn’t prevent them from tracking you, it just removes local history and cached stuff.
That disclaimer announcement just screams lazy IT, or general management by your side.
My bet is that FF has some privacy and/or adblocking features that this company doesn’t like.
There are a few features that FF doesn’t have that chrome does, but it mostly involves video streaming. Adblocking is likely the reason though.
Source: am front end dev
if you can’t even be arsed to fix your website i certainly can’t be arsed to buy from you
Please be aware it is Firefox with the “known bugs” lol
It’s not super difficult to just make a standards compliant website. I always wonder how in this day and age people manage to create professional websites with browser specific bugs.
There’s likely zero bugs, but Firefox has more ways to block ads and trackers from affecting you, which is likely to real reason they don’t want it being used.
There are quite a lot of quirks with how browser (or rather rendering engines) interpret CSS, and in quite a few places the spec is ambiguous. So there is no “correct” way of implementing it.
But, this is either just them being lazy or bad mangement.
I’ve had to debug a PDF viewer on a site once. Getting that to work across multiple versions of multiple browsers was a nightmare and I never managed to figure it out. Latest versions are mostly fine (except for mobile safari), but even 1yo versions of browsers are just broken.
Maybe I’m missing something, but it got bad enough that one of the “potential solutions” I was considering involved figuring out how to compile a C based pdf renderer thingy into WASM and embedding it in the app.
This was about 7 months ago.
I agree though, add to cart should NOT behave differently across browsers in 2024.
lmao write your website better then. That popup sure looks like its working
“Hello! If you are the operator of this site, it has known bugs with browsers other than chrome. Please consider doing your job and building for use cases other than the majority one when making your website, because it is 2024 and not 1994. If you are unable to, then consider using simpler website builders like Squarespace, which are known to work across a number of browsers. Thanks!”
This is the laziest dev work. And somehow they’ve convinced the owner that this is fine and got paid.
In a way, you have to admire the grift. At the same time, fuck 'em.
Remember the Internet Explorer domination?
deleted by creator
That’s a very weird of saying “we use a lot of non-standard code practices in our software”.
“We haven’t figured out how to violate Firefox user privacy protocols yet, so just go ahead and switch to the browser we can easily exploit. K? That cool?”
It’s time to get rid of the part of user-agent strings that identifies which browser you’re using. It should only include things like mobile/desktop, version of html supported, and JavaScript version supported.
It’s not that simple. A lot of browser “standards” are standards in that they achieve the same end result, but for whatever reason they take a different approach to getting to that result, so you often end up needing browser specific code. This is especially the case with CSS, which is why so many “standard” CSS properties still need a “-moz” or a “-webkit” version as well, decades in. The only way the website can know if they’re running the correct code for that browser is if they know what browser is being used, hence user agents. This is the reason that pop ups like this exist at all; sure they were lazy as fuck to not properly support Firefox, absolutely, but they wouldn’t have needed to support Firefox specifically at all if browsers could just get their shit together and fix the “standards”.
I would fucking cry tears of joy if browsers could standardize enough that writing browser specific code and needing the user agent was a thing of the past, but I really don’t see it happening any time soon.
Definitely not.
I have to version check to workaround Chrome, FireFox and Safari bugs. Some things they fix and I can flag around version (eg: FF113 has buggy focus detection with Web Components), but some just have never been fixed (eg: Firefox does not support animated styles with CSS variables in Web Components).
That’s not to pick on FireFox. Chrome doesn’t support scrolling two elements simultaneously which breaks any type of fancy horizontal scrolling in horizontal tabs. Safari has some buggy implementation with ARIA tags for Web Components and
[type=range]doesn’t follow spec formin.If we were going to just not support new features because browsers are buggy, we’d never get any new features. It’s better to feature detect and that includes knowing what versions need workarounds.
“a lot of known bugs”
Our storefront was coded with bloated javascript, runs like shit, and Chrome and Edge are good at hiding how bad it is :)
I’ve tested Firefox’s performance recently and it’s gotten super close to Blink/V8 in terms of performance, it even works better than those on my machine. So even if the website is coded like a turd there ain’t much reason anymore it wouldn’t work perfectly fine on Firefox
Unless you’re doing something really fucked with the code that I can’t think of right now
Or you’re deliberately making it slow when you detect someone visiting your site from Firefox
Thanks, YouTube
I’ve tested Firefox’s performance recently and it’s gotten super close to Blink/V8 in terms of performance, it even works better than those on my machine.
Same. In fact, I originally switched back to Firefox on my personal machine specifically because Chrome was making my laptop sound like an airplane taking off, even with only a single tab open. After the switch, I was able to open multiple tabs and even run other programs at the same time without a problem.
Come for the speed, stay for the privacy.
“Hey there, we can’t build a functional website, but just go ahead and give us your email address. MK?”
Absolutely no capitalization? That always makes me back away. You can’t even be bothered to make a proper sentence?
Yeah it’s a zoomer thing. Literally saw posts on Reddit about girls freaking out because some guy used that punctuation.
Probably their style. It kind of works
It’s a writing style. I like it. I even turn off auto-capitalization on my phone keyboard so my chats are all lowercase.
Chiming in to say that I agree with you! Texting in lowercase just feels right to me, especially with friends and family.
I don’t agree with you. But damn. you’re downvoted for doing what you like.
Ah, it is a bit disheartening to see how differing opinions are treated here sometimes. But hey, gotta be the change you want to see, right?
“yeah lets just ask our customers to switch browser instead of fixin our website. That will get the job done” I wonder how they came up with this
I build websites, and even when we supported Internet explorer 6, my company wouldn’t allow us to display a message like this. Anyone who ever developed a website for IE6 would know that if it were ever appropriate to display such a message, it was for IE6. It was atrocious beyond words. They ignored most of the standards and the browser was also just a security nightmare, yet still just on principle alone the idea was always shot down.
Somewhere there’s a very confused executive wondering why their bounce rate is so high.
But my ActiveX applets!
Java applets 4 life!
“Why spend thousands of dollars on paying someone to fix it when we can pay them hundreds to spend an hour writing a dialog box?” - Some storefront owner
