The Web Request API will still be available and still be able to provide information about all network requests fired by the browser … as opposed to what those announcements state, the deprecation of the blocking ability of the webRequest API accomplishes nothing privacy-wise for content blockers since they will *still* require broad hosts permissions.".
Google has begun testing their upcoming extension manifest V3 in the the latest Chrome Canary build, and with this initial 'alpha' release, developers can begin testing their extensions under the upcoming specification.Error when using unsupported APIs If you switch the extension to use a service_worker instead then the extension loads properly into Google Chrome.
The discovery was made by security researcher Sam Jadali, who told me at the time that Google’s Manifest V3 does not solve this specific problem: “It has some improvements however it explicitly states that server communication (potentially changing extension behavior) will still be allowed.
Chromium developer advocate Simeon Vincent confirmed that the first preview would be available for the Google developer Canary channel in late July or start of August. Microsoft is currently asking users whether they want built in ad blockers, while Brave has already said it won’t be taking on the Manifest V3 changes.
In response to concerns raised last month by the developers of the EFF's Privacy Badger extension, Simeon Vincent, developer advocate for Chrome extensions at Google, last week published an update on the company's Manifest v3 plan.
In a note posted Tuesday to the Chromium bug tracker, Raymond Hill, the developer behind uBlock Origin and uMatrix , said the changes contemplated by the Manifest v3 proposal will ruin his ad and content blocking extensions, and take control of content away from users.
Raymond Hill, known as Gorhill online, the author of the popular content blockers uBlock Origin and uMatrix, voiced his concern over some of the planned changes; these changes, if implemented as proposed currently, remove functionality that the extensions use for content blocking.
Beside causing uBO and uMatrix to no longer be able to exist, it's really concerning that the proposed declarativeNetRequest API will make it impossible to come up with new and novel filtering engine designs, as the declarativeNetRequest API is no more than the implementation of one specific filtering engine, and a rather limited one (the 30,000 limit is not sufficient to enforce the famous EasyList alone).