Everything worked perfectly as it always does.

  • 1984@lemmy.today
    link
    fedilink
    arrow-up
    9
    ·
    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
      3
      ·
      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…

    • Ottomateeverything@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      10 months ago

      It’s probably all the new generation of programmers/management - you would think they would listen to the lessons passed down but… Nope.

      • Muehe@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        10 months ago

        Depressingly, the message that GHG emissions are heating up the planet has been passed down for over a hundred years now. People just aren’t very good with passed down messages in general.