Yes, that is one of the features of MV3.I understand that MV3 extensions are only updated with the new release and not on a daily basis.
This isn't necessarily @gorhill's fault, but rather the limitations of MV3 architecture and, importantly, Chrome/Chromium and Edge bugs. The same applies to Privacy Badger and other ad blockers,e.g., PB's Google and Facebook link tracking are broken due to these. Gorhill doesn't even bother to publish UBOL in Firefox anymore.It seems that the developer of uBlock Origin Light has not given it the same attention and effort as uBlock Origin.
Will the proposed Manifest V3 changes to Chrome break Privacy Badger? · Issue #2273 · EFForg/privacybadgerOur Edge and Firefox versions are still MV2. The main reason for staying on MV2 is that MV3 is buggy.
Edge adds its own bugs on top of ones it inherits from Chrome (for example). I am sure Firefox's MV3 implementation is similarly buggy (for example).
At some point we will either be forced to migrate, or MV3 will become less buggy and more fully featured than MV2 (at least for Privacy Badger's immediate needs), in which case we will migrate voluntarily.
Will the proposed Manifest V3 changes to Chrome break Privacy Badger? · Issue #2273 · EFForg/privacybadgerWe are looking forward to releasing an MV3/DNR bug fix for #3147 soon. We are still unable to do anything about a bunch of known MV3 bugs because we need Google to fix them in Chrome and as we warned fixing MV3/DNR bugs is clearly not a priority for Google.
Last edited:




