How about no?

"Morningwitch"

"Firefox's privacy features interferes with our trackers"

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

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's probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but.... Nope.

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.

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

I use my separate pr0n browser for this kind of sites. It's set up to completely reset every time.

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

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.

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.

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

Imagine being this petty.

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

In a way, you have to admire the grift. At the same time, fuck 'em.

As a webdev, Safari has taken the place of IE now.

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.

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

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.

It's not that simple. A lot of browser "standards" are standards in that they achieve the same end result, but for whatever reason they take a different approach to getting to that result, so you often end up needing browser specific code. This is especially the case with CSS, which is why so many "standard" CSS properties still need a "-moz" or a "-webkit" version as well, decades in. The only way the website can know if they're running the correct code for that browser is if they know what browser is being used, hence user agents. This is the reason that pop ups like this exist at all; sure they were lazy as fuck to not properly support Firefox, absolutely, but they wouldn't have needed to support Firefox specifically at all if browsers could just get their shit together and fix the "standards".

I would fucking cry tears of joy if browsers could standardize enough that writing browser specific code and needing the user agent was a thing of the past, but I really don't see it happening any time soon.

Definitely not.

I have to version check to workaround Chrome, FireFox and Safari bugs. Some things they fix and I can flag around version (eg: FF113 has buggy focus detection with Web Components), but some just have never been fixed (eg: Firefox does not support animated styles with CSS variables in Web Components).

That's not to pick on FireFox. Chrome doesn't support scrolling two elements simultaneously which breaks any type of fancy horizontal scrolling in horizontal tabs. Safari has some buggy implementation with ARIA tags for Web Components and [type=range] doesn't follow spec for min.

If we were going to just not support new features because browsers are buggy, we'd never get any new features. It's better to feature detect and that includes knowing what versions need workarounds.

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

Yeah it's a zoomer thing. Literally saw posts on Reddit about girls freaking out because some guy used that punctuation.

Probably their style. It kind of works

It's a writing style. I like it. I even turn off auto-capitalization on my phone keyboard so my chats are all lowercase.

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

Works OK now, I just tried it.

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.

"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

Great dashboard:

Some gross monopolistic abuses in there… from the Android section alone:

Potion seller, give me your strongest potions

It's a clothing brand.

I found this site from a blog recommending a few brands. They didn't have what I wanted but the fact I was greeted by this was good enough to screenshot.

Tried it just now, didn't get an error either.

In the US I didn't see that popup either, just that notice on the page from my other comment.

Not really, it's a sorry not sorry kinda apology

"We are sorry, as a customer, you don't live up to our standards"

The URL is in the picture.

https://shop.morningwitch.com

did they try casting a spell to fix it?