Everything worked perfectly as it always does.
No, Firefox doesn’t have bugs with your store. Your store has bugs.
“Morningwitch”
“Firefox’s privacy features interferes with our trackers”
Classy to blame Firefox for bugs in their code :)
If devs write code for Chrome, yeah, maybe then it doesn’t work in Firefox guys…
We had exactly this situation in the 90s with internet Explorer… But new devs need to relearn lessons of course.
It was different in the case of IE though. It was actually atrocious and not standards compliant in many many ways.
Today, chrome and FF both support standards fairly well and when things don’t work in FF it’s usually either that you wrote fragile code, or there’s a slight difference from chrome that technically isn’t a standards compliance issue. Testing in both of those browsers isn’t hard and should be the norm. I’ve had projects where I had to test in IE, chrome windows, chrome android, FF, safari Mac, safari iPad OS, and safari iOS all at the same time. And yes there are differences between those last two, because apple makes a shitty web browser.
If you can’t test in two browsers, you’re just a bad web developer…
Absolutely this, nothing but pure laziness. I had a really weird specific issue on iOS Safari with one of my projects, and I own literally nothing Apple. Instead of just accepting shits fucked on iOS, I got my hands on a borrowed Mac so I could use xCode and actually find the issue.
…then again, that project ended up dead in the water at like 95% completion and I never got paid for the work I’d already finished, so maybe the joke IS on me and I should’ve been a lazy fuck.
Sounds like you might want to add some sort of terms of agreement to your estimates. I built sites that never saw the light of day, but that is entirely up to the client. A site not being live doesn’t mean my client doesn’t need to pay me.
It was for a family friend who is disabled and unable to work a normal job, so me and my brother(also a dev on this) agreed to be paid on project completion. Long story short, she wasn’t able to pay so the final bug fixes were never done, and the code has been left to rot. Under different circumstances I’d be putting pressure to get at least some payment, but it’s pointless imo.
Lesson learned though, not doing that again.
It could be they were using new features chrome added which Firefox had as experimental when they wrote it. Firefox recently promoted those features to stable.
It could be but then it’s even worse judgement. They basically don’t care if Firefox users can view their web site, and that’s one thing, but blaming it on Firefox is kind of rich, instead of taking responsibility for their decision. :)
It’s probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but… Nope.
Depressingly, the message that GHG emissions are heating up the planet has been passed down for over a hundred years now. People just aren’t very good with passed down messages in general.
See also: measles vaccinations.
You’re assuming that lessons are being passed down.
firefox has a lot of bugs with our store
Well, I think you got that backwards.
At least they seem to be working on it. Directing Firefox users to use a different browser in the mean time, temporarily, seems reasonable even if the language on that popup is a bit imprecise.
I did try adding a shirt to the cart and yeah, it added the wrong size. I’d have to switch to chrome to successfully complete an order at the moment. It’s unfortunate, but as long as they’re trying to fix it I don’t see any point in feeling outraged.
I did try adding a shirt to the cart and yeah, it added the wrong size. I’d have to switch to chrome to successfully complete an order at the moment. It’s unfortunate, but as long as they’re trying to fix it I don’t see any point in feeling outraged.
As a software developer, if just trying to add a single item to a cart is buggy, then that’s definitely something to feel outraged about, software development wise (not literally outraged, but definitely a strong “WTF!?” response).
It’s actually really amazing that a bug would manifest in one browser and not another, when just adding an item to a cart. You have to work really hard to make something like that not work correctly.
Yeah seriously, what is so special about what they’re doing here that it has a browser-specific bug?
This isn’t like 20 years ago where browsers had tons of experimental and custom extensions to HTML and JavaScript in them. It’s all standard now.
It’s all standard now.
The reason Microsoft surrendered to Google and adopted Chromium is they couldn’t keep up with Google’s changes to standards and proprietary extensions.
There are still several css differences between chrome, ff and safari. It’s a pain to develop for them, but it is possible
I wouldn’t feel safe entering my credit card information into a site that can’t even support Firefox, those are just the bugs they’re willing to tell you about…
Qewl, that’s actually a lot better than not even addressing it.
How is a function like adding an item to an array failing from one browser to another??
The bug is they can’t track you well enough
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
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.
Do you have an example of a quirk where Chrome and Firefox treat something in the spec differently? I haven’t seen that in a while.
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!”
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
Imagine being this petty.
Correction: your store has a lot of known bugs with Firefox
“firefox has known bugs with our store”
it’s not my fault you have trouble with designers
also brb bookmarking that site
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?
As a webdev, Safari has taken the place of IE now.
I’m assuming you mean as the thing we use to download FF?
-or is that the joke?
Safari? Really?
Must be the mobile version.
Safari is the worst because apple apparently refuses to update their browser outside an IOS/macOS update. So stupid.
Safari is a browser not a system app. It should be affected by system updates at all.
It’s the IE effect in more ways than one. Apple makes money from apps, and by having a monopoly on which app store you can use. Therefore it’s in their interest to nerf the browser as much as they can get away with it, and why they force third party browsers to use the Safari rendering engine under the hood.
by having a monopoly on which app store you can use
Not for long, at least in the EU.
Therefore it’s in their interest to nerf the browser as much as they can get away with it,
This is also why PWAs don’t work well on iOS. I think they still don’t even support notifications.
We wanna crawl up your butt with a microscope and the fox makes it extremely difficult
