2 ms·
Nothing, except for that it may stop working in Chrom[e|ium] next year when Google kills the current standard for web extensions. There's been some work done o
by jeroenhd 4y ago
Nothing, except for that it may stop working in Chrom[e|ium] next year when Google kills the current standard for web extensions.
There's been some work done on fixing this issue (https://github.com/uBlockOrigin/uBlock-issues/issues/338 https://github.com/uBlockOrigin/uBlock-issues/issues/338) but the architecture of content blocking extensions will need to change to facilitate Google's new requirements.
- ajvs 4y agoThey don't have to. I think gorhill recognises it's simply unfeasible to produce an effective content blocker on MV3, and I hope he puts his foot down and doesn't take on the maintenance burden of an additional nerfed browser extension. If web devs want to make web experiences worse in Firefox by issuing warnings everywhere, then Firefox can even the score by having a useable ad-free experience.