Everything worked perfectly as it always does.

  • 1984@lemmy.today
    0·
    6 months ago

    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.

    • unalivejoy@lemm.eeEnglish
      0·
      6 months ago

      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.

      • 1984@lemmy.today
        0·
        6 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. :)

    • TrickDacy@lemmy.world
      0·
      6 months ago

      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…

      • Perfide@reddthat.com
        0·
        6 months ago

        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.

        • ignism@lemmy.world
          0·
          6 months ago

          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.

          • Perfide@reddthat.com
            0·
            6 months ago

            It was for a family friend who is disabled and unable to work a normal job, so me and my brother(also a dev on this) agreed to be paid on project completion. Long story short, she wasn’t able to pay so the final bug fixes were never done, and the code has been left to rot. Under different circumstances I’d be putting pressure to get at least some payment, but it’s pointless imo.

            Lesson learned though, not doing that again.

  • Honytawk@lemmy.zip
    0·
    6 months ago

    Strange, I don’t get that pop-up with my Firefox.

    Might be because I am from Europe

    • Bilb!@lem.monsterEnglish
      0·
      6 months ago

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

  • const_void@lemmy.ml
    0·
    6 months ago

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

  • Bilb!@lem.monsterEnglish
    0·
    6 months ago

    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.

    • Cosmic Cleric@lemmy.world
      0·
      6 months ago

      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.

      • 4am@lemm.ee
        0·
        6 months ago

        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.

    • InFerNo@lemmy.ml
      0·
      6 months ago

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