Everything worked perfectly as it always does.

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    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.

    • TrickDacy@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      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
        link
        fedilink
        arrow-up
        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
          link
          fedilink
          arrow-up
          1
          ·
          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
            link
            fedilink
            arrow-up
            1
            ·
            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.

  • Bilb!@lem.monster
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    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.

    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.

    • Cosmic Cleric@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      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
        link
        fedilink
        arrow-up
        1
        ·
        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.

  • const_void@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

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

  • newbeni@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

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

  • reddig33@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    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.

  • olutukko@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 months ago

    “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

    • TrickDacy@lemmy.world
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      6 months ago

      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.

    • rwhitisissle@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

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