this post was submitted on 20 Jan 2024
1396 points (98.7% liked)

Firefox

17898 readers
62 users here now

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

founded 4 years ago
MODERATORS
 

Everything worked perfectly as it always does.

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 471 points 10 months ago (2 children)

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

load more comments (2 replies)
[–] [email protected] 261 points 10 months ago* (last edited 10 months ago) (6 children)

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.

[–] [email protected] 44 points 10 months ago (3 children)

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

load more comments (3 replies)
[–] [email protected] 16 points 10 months ago (1 children)

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.

[–] [email protected] 48 points 10 months ago

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

load more comments (4 replies)
[–] [email protected] 157 points 10 months ago* (last edited 10 months ago)

firefox has a lot of bugs with our store

Well, I think you got that backwards.

[–] [email protected] 128 points 10 months ago* (last edited 10 months ago) (4 children)

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.

[–] [email protected] 70 points 10 months ago (1 children)

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.

[–] [email protected] 34 points 10 months ago (2 children)

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.

load more comments (2 replies)
[–] [email protected] 15 points 10 months ago* (last edited 10 months ago)

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

load more comments (2 replies)
[–] [email protected] 104 points 10 months ago

The bug is they can't track you well enough

[–] [email protected] 99 points 10 months ago (2 children)

Firefox has a "bug" that makes our tracking code not work. Please switch to Chrome so we can track you.

load more comments (2 replies)
[–] [email protected] 89 points 10 months ago* (last edited 10 months ago) (2 children)

That disclaimer announcement just screams lazy IT, or general management by your side.

[–] [email protected] 31 points 10 months ago

My bet is that FF has some privacy and/or adblocking features that this company doesn't like.

[–] [email protected] 15 points 10 months ago* (last edited 10 months ago)

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

[–] [email protected] 84 points 10 months ago (4 children)

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.

[–] [email protected] 63 points 10 months ago

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.

load more comments (3 replies)
[–] [email protected] 82 points 10 months ago (2 children)

if you can't even be arsed to fix your website i certainly can't be arsed to buy from you

[–] [email protected] 15 points 10 months ago

Please be aware it is Firefox with the "known bugs" lol

load more comments (1 replies)
[–] [email protected] 80 points 10 months ago (1 children)

lmao write your website better then. That popup sure looks like its working

[–] [email protected] 33 points 10 months ago* (last edited 10 months ago)

“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!”

[–] [email protected] 68 points 10 months ago

We wanna crawl up your butt with a microscope and the fox makes it extremely difficult

[–] [email protected] 62 points 10 months ago

Correction: your store has a lot of known bugs with Firefox

[–] [email protected] 58 points 10 months ago (1 children)

This is the laziest dev work. And somehow they've convinced the owner that this is fine and got paid.

load more comments (1 replies)
[–] [email protected] 57 points 10 months ago* (last edited 10 months ago)

"firefox has known bugs with our store"

it's not my fault you have trouble with designers

also brb bookmarking that site

[–] [email protected] 55 points 10 months ago (7 children)

Remember the Internet Explorer domination?

load more comments (7 replies)
[–] [email protected] 50 points 10 months ago (4 children)
  1. Just visited the site with FF, and got no such error. It's a Shopify site, and I'm sceptical.
  2. If it's a typical Shopify SBO, it could easily be a single person - the owner - working out of their house. There is no developer, except those employed by Shopify.

The owner probably populated the store themselves; the entirety rest of their computer experience brobably consists of browsing Wiccan forums, Instagram, and Twitter. And yet, they figured out how to open an online shop and start a business doing something they're passionate about.

Educated guesses, but poking around a bit on the site & following links gives good evidence this person is a person, not a company, and doesn't employ anyone, much less programmers.

And I've never had a Shopify site pop up a message like this. I think OP hit a fluke, or a MITM, or (most likely) has a virus.

load more comments (4 replies)
[–] [email protected] 50 points 10 months ago (1 children)

That's a very weird of saying "we use a lot of non-standard code practices in our software".

[–] [email protected] 20 points 9 months ago

"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?"

[–] [email protected] 43 points 10 months ago (3 children)

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.

[–] [email protected] 14 points 10 months ago (1 children)

There is no uniform "HTML version", "JavaScript version" or "CSS version" that describes which web APIs are implemented. Browser engines support some features that others don't support and vice versa.

load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 42 points 9 months ago

"Hey there, we can't build a functional website, but just go ahead and give us your email address. MK?"

[–] [email protected] 40 points 10 months ago (1 children)
[–] [email protected] 39 points 10 months ago (4 children)

Our storefront was coded with bloated javascript, runs like shit, and Chrome and Edge are good at hiding how bad it is :)

load more comments (4 replies)
[–] [email protected] 39 points 10 months ago (7 children)

Absolutely no capitalization? That always makes me back away. You can't even be bothered to make a proper sentence?

load more comments (7 replies)
[–] [email protected] 35 points 10 months ago (5 children)

Everyone browse that website and when they see the traffic all using firefox. They will get the message.

[–] [email protected] 15 points 10 months ago (3 children)

Quite the opposite - no one browse that site because it's not standards compliant and/or privacy compliant.

load more comments (3 replies)
load more comments (4 replies)
[–] [email protected] 33 points 10 months ago (2 children)

"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

[–] [email protected] 15 points 10 months ago (3 children)

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.

load more comments (3 replies)
[–] [email protected] 14 points 10 months ago* (last edited 10 months ago)

"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

[–] [email protected] 27 points 10 months ago

That store is hosted on Shopify. I'm quite confident they handle Firefox just fine. The customization(s) the company made to defaults on the other hand...

[–] [email protected] 26 points 10 months ago

I'm having a 90's Internet Explorer flashback.

[–] [email protected] 24 points 10 months ago

I would never shop there again. What a joke.

[–] [email protected] 24 points 10 months ago* (last edited 10 months ago) (1 children)

Put it up on that new dashboard thing they set up

Edit: here it is https://blog.mozilla.org/netpolicy/2024/01/19/platform-tilt/

load more comments (1 replies)
[–] [email protected] 22 points 10 months ago

This seems like like a perfect opportunity to visit your competitors website!

[–] [email protected] 20 points 10 months ago

It's like saying Linux is bad for games.

[–] [email protected] 16 points 10 months ago

That's it, they just lost a prospective customer!

[–] [email protected] 15 points 10 months ago

time to bust out user agent switcher.

[–] [email protected] 15 points 10 months ago

"... but sign up for our newsletter!"

load more comments
view more: next ›