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