Comment on Google Chrome’s plan to limit ad blocking extensions kicks off next week

mysticpickle@lemmy.ca ⁨2⁩ ⁨years⁩ ago

• onlinepersona@programming.dev ⁨2⁩ ⁨years⁩ ago

  Who knows… Firefox might just follow suit. If devs have to write their extensions one for Chrome and once for Firefox, the Firefox one will probably be the first to die.

  Anti Commercial-AI license

  source

  • Andromxda@lemmy.dbzer0.com ⁨2⁩ ⁨years⁩ ago

    That’s not how it works. Firefox has full support for Manifest v3 extensions, but it does also support MV2 at the same time, and aims to keep MV2 support alive in the future.

    source
  • Midnitte@beehaw.org ⁨2⁩ ⁨years⁩ ago

    Not if more people use FireFox…

    Firefox also supports mobile extensions, unlike Chrome.

    source

    • fatalError@lemmy.sdf.org ⁨2⁩ ⁨years⁩ ago

      Unfortunately, as much as I like and use firefox on both pc and mobile, chrome and chromium based browsers dominate the market. It doesn’t help that they come pre-installed in both cases.

      source
  • 30p87@feddit.de ⁨2⁩ ⁨years⁩ ago

    Then there will be thousands, millions of people continuing development of FF extensions.

    source
  • lemmyvore@feddit.nl ⁨2⁩ ⁨years⁩ ago

    Isn’t that already how it works? Are there extensions trust work unchanged on both browsers? At the very least they’d have to maintain them on both addon stores.

    source

    • Andromxda@lemmy.dbzer0.com ⁨2⁩ ⁨years⁩ ago

      There’s a common specification called WebExtension, which is used by all modern browsers. Firefox had their own API (XUL/XPCOM) before that, but they deprecated it in 2017. Safari also used to have its own system for extensions, but it’s been deprecated since 2019. The Manifest API is a subset of WebExtension, which defines an extension.

      source