Rendered at 10:12:43 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
seaman100 20 hours ago [-]
"Some" is doing a lot of work in that headline. Manifest V3 on Android Chromium is constrained by what's possible in the WebView/CDS API surface — so I'm curious which subset Vivaldi chose to prioritize. content_scripts and popups generally work, but anything touching the chrome.* API beyond storage/tabs gets awkward. Worth a side-by-side with how Kiwi Browser handled this before it went unmaintained.
akazantsev 13 hours ago [-]
Hopefully, they will do just what Brave did - embed an ad blocker compatible with uBlock lists right into the browser. This way, Manifest V3 might blow up in Google's face if a sufficient number of browsers come with ad blockers out of the box.
That being said, they are not talking about Manifest V3 extensions. It's just that they can't test all the extensions and will have to work out the issues as they implement the extension API for mobile.
Drakim 1 hours ago [-]
> This way, Manifest V3 might blow up in Google's face
I'm sure Google will have a new important security announcement at that point. All of these forked browsers can no longer have the widevine certification unless they conform to certain ad-friendly changes.
That being said, they are not talking about Manifest V3 extensions. It's just that they can't test all the extensions and will have to work out the issues as they implement the extension API for mobile.
I'm sure Google will have a new important security announcement at that point. All of these forked browsers can no longer have the widevine certification unless they conform to certain ad-friendly changes.