For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.

What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.

    • A_Random_Idiot@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 hours ago

      I’ve only ever encountered one website where Firefox didnt work.

      and that was because the website was coded maliciously to reject firefox… a plugin to make it think firefox was chrome and suddenly it ran fine.

      • Sckharshantallas@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 hours ago

        Well I did, the Amazon Prime Video has many weird behaviors on Firefox compared to the Chromium engine, even YouTube used to have before.

        Any web developer knows it isn’t as simple as “code once, work everywhere”. If companies don’t test on Firefox (which is a reality nowadays given its small market share) bugs happen in very weird and unusual ways.

        • A_Random_Idiot@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours ago

          Only issue I’ve ever had with Amazon Video was the fact they artificially limit resolution to 320p for people on linux, regardless of browser.