Comment by lxgr
5 hours ago
What exactly is your gripe with MV3?
Many people seem to treat it synonymously with "no more procedural request blocking", but that's not a thing Mozilla ever did:
> For Manifest V3 extensions, Chrome no longer supports the "webRequestBlocking" permission (except for policy-installed extensions). Instead, the "webRequest" and "webRequestAuthProvider" permissions enable you to supply credentials asynchronously. Firefox continues to support "webRequestBlocking" in Manifest V3 and provides "webRequestAuthProvider" to offer cross-browser compatibility.
The permission model also seems much more reasonable (less permissions have to be requested upfront at install time) than MV2, so I actually hope Firefox does deprecate it at some point.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
https://blog.mozilla.org/en/firefox/firefox-manifest-v3-adbl...
> What exactly is your gripe with MV3?
Running an adblocker is the defining feature of the extensions API. ublock origin has 5x as many users as the second-most-popular extension [1]
Supporting ublock isn't just a nice-to-have add-on feature for an extension API, it's literally the only thing most users care about.
[1] https://addons.mozilla.org/en-GB/firefox/search/?promoted=re...