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”
firefox has a lot of bugs with our store
Well, I think you got that backwards.
Use Ublock Origin and remove the banner. Bad banners dont actually block anything.
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.
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 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…
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.
How is a function like adding an item to an array failing from one browser to another??
“Hey there, we can’t build a functional website, but just go ahead and give us your email address. MK?”
if you can’t even be arsed to fix your website i certainly can’t be arsed to buy from you
Imagine being this petty.
Firefox has a “bug” that makes our tracking code not work. Please switch to Chrome so we can track you.
Remember when shopping sites didn’t need 200mb of javascript libraries to work?
This seems like like a perfect opportunity to visit your competitors website!
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?”
Correction: your store has a lot of known bugs with Firefox
Hey would you be willing to pass the site you found this on so we can all studiously avoid it? :)
The URL is in the picture.
Hey at least they apologize! 🤣
“We are sorry, as a customer, you don’t live up to our standards”
Everyone browse that website and when they see the traffic all using firefox. They will get the message.
Quite the opposite - no one browse that site because it’s not standards compliant and/or privacy compliant.
Best of all worlds: browse the site, create an order, don’t purchase anything.
“Why are all of these people abandoning their cart?”
“I don’t know, but they’re all Firefox users.”
“Ugh, friggin nerds”
