“UBO Minus (MV3)” – An Experimental uBlock Origin Build for Manifest V3
I approve (of both the release and the name).<p>I see plenty of folks in here lamenting this release at all - in the hopes that the lack of it will push folks to Firefox.  It won't.  Those who care about this are already on Firefox, and frankly - Firefox isn't going to be the answer here (to be clear, this is opinion).<p>I'm also not thrilled at manifest v3, although for very different reasons than the adblocking limitations - I do lots of extension development, and I think the service worker approach taken is a <i>bad</i> mistake, forcing a distributed consensus model onto extensions without understanding the limitations that model imposes given how often extensions span multiple js contexts (across tabs/frames/content_scripts/windows/etc).<p>Frankly - the environment is also still riddled with bugs... everything from docs that are wrong, to <i>serious</i> issues like a service worker not activating on simple, basic, required events (like chrome.action.onClicked, which is literally about as basic as it gets for extensions).<p>Overall - my first impression of the manifest v3 upgrade was fairly neutral (it's not really solving any of my pain points, and it requires a lot of changes to support - but it seemed functional).  My opinion after porting several large extension projects to the space is... bad.  It's a bad set of changes as implemented in chromium right now.