Everything worked perfectly as it always does.

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

    • InFerNo@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

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

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

  • feoh@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    10 months ago

    Hey would you be willing to pass the site you found this on so we can all studiously avoid it? :)

  • const_void@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    10 months ago

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

  • kratoz29@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    10 months ago

    That disclaimer announcement just screams lazy IT, or general management by your side.

    1. Just visited the site with FF, and got no such error. It’s a Shopify site, and I’m sceptical.
    2. 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.

    • rwhitisissle@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      10 months ago

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