Hacker News new | ask | show | jobs
by Glench 1655 days ago
Yeah this is a very awkward release, and not just because MV3 cripples the most important extensions (adblockers).

Firefox also hasn't released MV3 support yet so extensions that are cross-browser can't be MV3, which will be really annoying when Chrome no longer accepts MV2 extensions.

I ran into this just yesterday when I tried to release an extension that removes those stupid fixed banners that take up vertical screen space when you're trying to read an article (https://addons.mozilla.org/en-US/firefox/addon/remove-floati..., https://chrome.google.com/webstore/detail/remove-floating-ba...). I tried to convert it to MV3 only to test on Firefox and find out it doesn't support MV3 :(

I also run https://extensionpay.com which lets developers easily take payments in their extensions without writing their own backend or paying for server costs. A lot of the developers using ExtensionPay in their extensions default to using MV3 since that's what Google says they should do, despite its limitations. It's a really sad state of affairs.

1 comments

Has Mozilla committed to supporting both versions into the future? Or do they intend to bend over?
You can read the details here: https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...

TLDR: They're officially going to support MV3 but also not going to deprecate the network blocking APIs that Google is.

Better questions is is Microsoft going to maintain v2 API in Blink/Chromium.