Everything worked perfectly as it always does.
No, Firefox doesn’t have bugs with your store. Your store has bugs.
“Morningwitch”
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
Qewl, that’s actually a lot better than not even addressing it.
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…
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.
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.
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.
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!”
deleted by creator
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
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 not be affected by system updates at all.
Can you even update Safari separately on iOS?Nevermind, read that as “people refuse” instead of “apple refuse”
Fuck Apple.
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.
- Just visited the site with FF, and got no such error. It’s a Shopify site, and I’m sceptical.
- 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.
I just visited with FF and got the error. Looking at the console, Firefox complains about some cookies misusing specific site attributes and actively rejects some cookies from that website entirely. That might be the source of the issue with the site’s “developer.”
Makes you wonder had the owner even managed to get enough code together to check the UA for Fx detection that launches a dialog window as I doubt Shopify has any built-in UA detection tools like this.
I remember thinking “hah, business majors, don’t they know everything is gonna be ruled by tech?” And then it turns out the tech nerds just work for the business majors still.
@tocopherol Reminds me of the Northwestern University football cheer, “We don’t cry, we don’t fuss. Someday you’ll all work for us!”
deleted by creator
