• henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    If your website only works with Chrome, it’s not a website. It’s a Chrome site.

    You didn’t design for the web. You designed for Chrome.

      • Lena@gregtech.eu
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        I agree that Chrome fucking sucks, but it’s disingenuous to call it unoptimized. Chrome and chromium-based browsers are as fast as or faster than Firefox. Although I agree that manifest V3 is horrible to the web as a whole and shouldn’t have been created.

    • Zagorath@aussie.zone
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months ago

      That’s not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.

      • Blue_Morpho@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        I don’t know the history of column span but the reason Firefox was “behind” on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.

        It was Google doing their variation of “embrace, extend, extinguish”

        It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.