• smeg
      link
      fedilink
      English
      arrow-up
      31
      ·
      edit-2
      7 months ago

      From the article:

      Firefox plans to support Manifest V3 because Chrome is the world’s most popular browser, and it wants extensions to be cross-browser compatible, but it has no plans to turn off support for Manifest V2.

      I doubt they’ll ever choose to shut down V2, but Google is already forcing their hand a little by making them require supporting V3 to stay relevant

    • Midnitte@beehaw.org
      link
      fedilink
      English
      arrow-up
      18
      ·
      7 months ago

      Not if more people use FireFox…

      Firefox also supports mobile extensions, unlike Chrome.

      • fatalError@lemmy.sdf.org
        link
        fedilink
        arrow-up
        6
        ·
        7 months 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.

    • 30p87@feddit.de
      link
      fedilink
      arrow-up
      13
      ·
      7 months ago

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

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 months 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.

      • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        8
        ·
        7 months 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.