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.

  • fizzle@quokk.au
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    27 days ago

    FF support is getting worse and worse though.

    Barely any of the sites I use for work support FF.

    Laugh all you want but shit is a bit fucked.

    Ladybird is our last best hope and its barely a glimmer.

    • Axolotl@feddit.it
      link
      fedilink
      English
      arrow-up
      8
      ·
      27 days ago

      Fun fact: many sites that say that they don’t support firefox lie, their sites usually support it but they never tested it or they deem firefox “less secure” or some bullshit, but with an useragent spoofer, they will work

      (Not all sites ofc)

      • fizzle@quokk.au
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        11
        ·
        27 days ago

        Fun fact: you don’t seem very bright.

        By “support FF” I mean “can be used in firefox or a derivative with comparable features to chrome”.

          • fizzle@quokk.au
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            27 days ago

            I’m not talking about sites that claim not to support FF. I’m talking about sites that have broken features when visited in FF.

    • [deleted]@piefed.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      27 days ago

      That isn’t FF support. That is chrome doing the same thing as Internet Explorer did by implementing non-standard functionality to abuse their market dominance.

      • fizzle@quokk.au
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        27 days ago

        Sure but if devs don’t test sites in Firefox then very they don’t support Firefox.

      • fizzle@quokk.au
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        13 days ago

        I’ve answered this so many times.

        Banks, my uni, accounting software I use at work.

        Its a well acknowledged and much discussed fact that the web is buggy with ff.

        • greyscale@lemmy.grey.ooo
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 days ago

          Wack. Its usually chrome that shits the bed. Or its because their app cant tolerate an adblocker.

          Doesn’t match up with my lived experience. Sorry for your loss.