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.

  • AlecSadler@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    13
    ·
    5 hours ago

    Good for you. I’ve been in tech for over 16 years and FF absolutely does not work well on ~25% of websites.

    • M0oP0o@mander.xyz
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      5 hours ago

      Been in tech longer then that (if for some reason we are doing that now) and I will officially call bullshit on that claim.

    • imetators@lemmy.dbzer0.com
      cake
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      5 hours ago

      I get it that tech people stumble upon these sites much more often than non-techies. My point was that if your parents are having website issues every other day (which implies they are not tech-savvy), then why would they even visit sites that are not FF-compatible. How many sites out of all the web do you think are not compatible with FF? Give an example of a normie site that wont work well with FF.

      On the other hand, if your parents are tech-savvy then why would they ask you why a website wont load properly? Do you get it that your statement counters itself?

      • AlecSadler@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        5 hours ago

        I have not been able to get proper payment processing to work with Portland area PGE in FF, ever. Across Windows, Linux, or Android (can’t speak for MacOS or iOS).

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

      Wait, really? The access cripplers are crazily powerful add-ons for the paranoid, like NoScript, not the browser itself. Like what example websites, specifically?

      • AlecSadler@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        5 hours ago

        Bare MVP is ublock+ stock FF. Even allowing 3rd party cookies and…

        • ~25% of local news sites don’t work right (Portland metro)
        • All internal work websites across all jobs don’t work right for the past ~6 years (not counting Gusto, ADP was hit or miss depending on the function, Paylocity was OK)
        • Multiple places I’ve lived rental payment sites don’t work
        • Portland metro utility payment sites don’t load right and to fill out proper fields required weird tabbing to off-page fields and guessing what is being entered
        • One city site for payments or reports would straight up not load in FF

        Y’all can burn me at the stake all you want, I don’t fucking care. I use FF daily and champion it, but to say it works 100% all the time for every site is just disingenuous.

        • munk@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          Just wanna say I’ve had similar experiences. I don’t think I’d put the number as high as 25% for myself, but my workplace’s internal sites and some local/utility sites are also broken on non-Chromium browsers.