Forum Discussion
Manifest V3: Web Request Changes
So, Google plan to introduce manifest v3 that limit extensions blocking capability by removing webRequest API and replacing it with super limited declarativeNetRequest. Please, please don't remov...
but microsoft chose to switch to chromium. they gave control to google who is the main contributor to chromium. they chose the path of little development 😞
They de-googled Chromium before integrating it into their Edge browser..
- I know they de-googled Chromium.
They don't review every commit and add each one. They have a set of patches. An apt Android browser comparison would be Kiwi to Bromite. btw Ungoogled Chromium exists but Microsoft did more than what Ungoogled Chromium has done iirc.- Microsoft did more than what Ungoogled Chromium has done iirc so that means it's good, right?
- Chromium is already the "de-googled" version of chrome.
microsoft "just" added the microsoft-stuff to chromium and some additonal features.
I doubt microsoft will add much effort into maintaining an api just for ad-blockers, and i doubt google will make it easy for chromium forks to add and maintain apis to bypass the new specifications.
But microsoft could at least increase the limit of rules that plugins can pass into the network-filter api.
The next version of chromium (v80) will contain the first changes from manifest v3, we will see how these changes will reflect into edge chromium.- "The next version of chromium (v80) will contain the first changes from manifest v3, we will see how these changes will reflect into edge chromium."
We can already see the changes in both Google chrome and Microsoft Edge. version 80 has been feature-locked for a long time now, you can see the changes in Microsoft Edge dev which is still on version 80 and Canary which is on version 81.
"microsoft "just" added the microsoft-stuff to chromium and some additonal features."
"Not" really
https://www.theverge.com/2019/4/8/18300772/microsoft-google-services-removed-changed-chromium-edge-browser
"i doubt google will make it easy for chromium forks to add and maintain apis to bypass the new specifications."
Brave, the privacy focused new browser is based on chromium, don't you think manifest V3 with all those flaws would literally end Brave's main feature and usefulness? the ability to block ads?- I dont think manifest v3 will end braves main features. As braves main focus is just this feature they will put effort into maintaining an "usefull" api for blocking ads.
But why should microsoft do? They do sell ads via bing themself.
