Everything worked perfectly as it always does.

473 points

No, Firefox doesn’t have bugs with your store. Your store has bugs.

permalink
report
reply
11 points

“Morningwitch”

permalink
report
parent
reply
6 points

“Firefox’s privacy features interferes with our trackers”

permalink
report
parent
reply
261 points
*

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.

permalink
report
reply
44 points

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…

permalink
report
parent
reply
10 points

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.

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply
16 points

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.

permalink
report
parent
reply
48 points

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. :)

permalink
report
parent
reply
12 points
*

It’s probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but… Nope.

permalink
report
parent
reply
14 points

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.

permalink
report
parent
reply
4 points

See also: measles vaccinations.

permalink
report
parent
reply
0 points

You’re assuming that lessons are being passed down.

permalink
report
parent
reply
157 points
*

firefox has a lot of bugs with our store

Well, I think you got that backwards.

permalink
report
reply
128 points
*

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.

permalink
report
reply
70 points

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.

permalink
report
parent
reply
33 points

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.

permalink
report
parent
reply
13 points
*

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.

permalink
report
parent
reply
4 points

There are still several css differences between chrome, ff and safari. It’s a pain to develop for them, but it is possible

permalink
report
parent
reply
15 points
*

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…

permalink
report
parent
reply
14 points

Qewl, that’s actually a lot better than not even addressing it.

permalink
report
parent
reply
2 points

How is a function like adding an item to an array failing from one browser to another??

permalink
report
parent
reply
104 points

The bug is they can’t track you well enough

permalink
report
reply

Firefox

!firefox@lemmy.ml

Create post

A place to discuss the news and latest developments on the open-source browser Firefox

Community stats

  • 2.6K

    Monthly active users

  • 965

    Posts

  • 18K

    Comments

Community moderators