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.

            • SolarMonkey@slrpnk.net
              link
              fedilink
              English
              arrow-up
              2
              ·
              edit-2
              5 months ago

              Those sites will be dead to me :)

              QR codes are like the popups of days gone by. With incredibly few exceptions, I refuse to scan them. They are so easy to redirect for nefarious purposes, and you can’t easily inspect the url to know, assuming thats something you even do. Also my phone case covers the camera and it’s a bitch to get open so I’m very choosy with what gets camera time.

    • fizzle@quokk.au
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months 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
        1
        ·
        5 months 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
          1
          ·
          4 months 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
            ·
            4 months 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.

    • pHr34kY@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      5 months ago

      The MV3 support in firefox is even stricter than in Chrome. I found that chrome will let you sidestep CSP to make an HTTP request. Firefox won’t.

      • WhyJiffie@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        I don’t understand what you found, but firefox still supports the web request blocking API for Mv3 extensions, which is what ublock needs.

        • pHr34kY@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          5 months ago

          I was debugging one of my favourite extensions this week to figure out why it didn’t work on firefox. It hadn’t been updated in years, so something changed in firefox in the last few months.

          I assume the Chrome version still works. I’m not installing it.

          • WhyJiffie@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

            if it hadn’t been updated in years then it will be an Mv2 extension, irrelevant to discussion of Mv3 strictness.