Re:AdGuard publishes the first ad blocker built on Manifest V3
by HWR_14 on Tuesday August 30, 2022 @11:06AM
(#32651348)
> Removing whatever misfeatures Google adds to Chrome is fairly straightforward.
Yes. But adding back in Manifest v2 isn't. Even MSFT claims that it's too much work for them.
Re:AdGuard publishes the first ad blocker built on Manifest V3
by NeverFade on Tuesday August 30, 2022 @03:47PM
(#32654235)
IIUC, the only problem with Mv3 is that they disabled the WebRequest API. A fork of Chromium that solves this problem will just have to re-enable the WebRequest API, which seems doable.
Re:AdGuard publishes the first ad blocker built on Manifest V3
by HWR_14 on Tuesday August 30, 2022 @04:27PM
(#32654630)
Isn't the lack of a WebRequest API one of the primary changes in Manifest v3?
The real danger to having a single codebase for the whole web is spec validation. Most web standards rely on two independent implementations. For newer technologies we could technically count WebKit and Blink as separate, but Gecko was providing an entirely separate codebase that isn't a fork of anything.
Remember how WebSQL was basically put out to pasture because it was just SQLite, warts and all, shoved inside the web sandbox? That's the sort of problem we'd rather avoid. Single-implementation standards tend to pick up bugs and misbehaviors from their implementation, since everyone winds up depending on implementation bugs rather than getting them fixed to match spec.