• invertedspear@lemm.ee
    link
    fedilink
    English
    arrow-up
    39
    ·
    9 months ago

    Which is kind of dumb, because if you target Firefox you are writing to a standards compliant browser that means your code should work on all other browsers. Chrome came when IE still owned the internet and their goal was to offer a faster browser that still worked, so now chrome has a bunch of hacks coded into it.

    • sysadmin420@lemmy.world
      link
      fedilink
      English
      arrow-up
      21
      ·
      9 months ago

      Sometimes the president or CEO just doesn’t give a shit even when devs tell them otherwise.

      Devs don’t always get a lot of choice when the upper management thinks chrome is better

      It’s why baracuda only really advertised in airport terminals everywhere.

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        10
        arrow-down
        2
        ·
        9 months ago

        Devs don’t always get a lot of choice when the upper management thinks chrome is better

        The devs can tell management they’ll make it work on Chrome while really making it work cross-browser. It’s not too hard to make a site cross-browser these days, except for Safari sometimes having weird bugs.

        • ThePowerOfGeek@lemmy.world
          link
          fedilink
          English
          arrow-up
          8
          ·
          edit-2
          9 months ago

          Pfft, who would do that? As a Firefox user myself I never would. Carve out a bit of time on the down-low to enhance cross-browser support on a website after management shortsightedly told me to just block anything other than Chrome? No no no! Not me!

          Of course as others here (including you) have pointed out, it’s much less of an issue these days. Though it does still happen, it’s nowhere near as bad as the IE days (that browser can burn in hell for all eternity!).