▲ 204 ▼ Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com) submitted 2 years ago by UngodlyAudrey@beehaw.org to c/technology@beehaw.org 44 comments fedilink hide all child comments
[–] mysticpickle@lemmy.ca 71 points 2 years ago (1 child) ::Laughs in Firefox:: permalink fedilink source hideshow 2 child comments replies: [–] onlinepersona@programming.dev 9 points 2 years ago (5 children) 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 permalink fedilink source parent hideshow 10 child comments replies: [–] Andromxda@lemmy.dbzer0.com 48 points 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. permalink fedilink source parent [+] smeg@feddit.uk 31 points 2 years ago* [deleted] permalink fedilink source parent [–] Midnitte@beehaw.org 18 points 2 years ago (1 child) Not if more people use FireFox... Firefox also supports mobile extensions, unlike Chrome. permalink fedilink source parent hideshow 2 child comments replies: [–] fatalError@lemmy.sdf.org 6 points 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. permalink fedilink source parent [–] 30p87@feddit.de 13 points 2 years ago Then there will be thousands, millions of people continuing development of FF extensions. permalink fedilink source parent [–] lemmyvore@feddit.nl 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Andromxda@lemmy.dbzer0.com 7 points 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. permalink fedilink source parent
[–] onlinepersona@programming.dev 9 points 2 years ago (5 children) 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 permalink fedilink source parent hideshow 10 child comments replies: [–] Andromxda@lemmy.dbzer0.com 48 points 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. permalink fedilink source parent [+] smeg@feddit.uk 31 points 2 years ago* [deleted] permalink fedilink source parent [–] Midnitte@beehaw.org 18 points 2 years ago (1 child) Not if more people use FireFox... Firefox also supports mobile extensions, unlike Chrome. permalink fedilink source parent hideshow 2 child comments replies: [–] fatalError@lemmy.sdf.org 6 points 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. permalink fedilink source parent [–] 30p87@feddit.de 13 points 2 years ago Then there will be thousands, millions of people continuing development of FF extensions. permalink fedilink source parent [–] lemmyvore@feddit.nl 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Andromxda@lemmy.dbzer0.com 7 points 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. permalink fedilink source parent
[–] Andromxda@lemmy.dbzer0.com 48 points 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. permalink fedilink source parent
[–] Midnitte@beehaw.org 18 points 2 years ago (1 child) Not if more people use FireFox... Firefox also supports mobile extensions, unlike Chrome. permalink fedilink source parent hideshow 2 child comments replies: [–] fatalError@lemmy.sdf.org 6 points 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. permalink fedilink source parent
[–] fatalError@lemmy.sdf.org 6 points 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. permalink fedilink source parent
[–] 30p87@feddit.de 13 points 2 years ago Then there will be thousands, millions of people continuing development of FF extensions. permalink fedilink source parent
[–] lemmyvore@feddit.nl 2 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] Andromxda@lemmy.dbzer0.com 7 points 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. permalink fedilink source parent
[–] Andromxda@lemmy.dbzer0.com 7 points 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. permalink fedilink source parent