Google Chrome browser privacy plan investigated in UK
Remember the discussion about Manifest V3, eliminating webRequest API [1] which results in Adblockers being thrown out of the Chrome ecosystem?<p>Guess what the state is, now, 1 year later ... the declarativeWebRequest API is still on hold; and it&#x27;s not supported outside of Beta Channel, and there are no plans to move it to stable. [2] Its documentation still states the same as it did half a year ago:<p>&quot;Note: this API is currently on hold, without concrete plans to move to stable. Use the chrome.declarativeWebRequest API to intercept, block, or modify requests in-flight.&quot;<p>... which effectively means that there&#x27;s no way to block or modify request&#x2F;response headers in Manifest V3, which is essential for Adblockers because they tend to override the Content-Security-Policy and remove headers like &quot;Cookie&quot; or &quot;Set-Cookie&quot; etc.<p>And now we have the Chrome Web Store moving ahead with the Manifest V3 rollout. [3]<p>[1] <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;docs&#x2F;extensions&#x2F;reference&#x2F;webRequest&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;docs&#x2F;extensions&#x2F;reference&#x2F;webRe...</a><p>[2] <a href="https:&#x2F;&#x2F;developer.chrome.com&#x2F;docs&#x2F;extensions&#x2F;reference&#x2F;declarativeWebRequest" rel="nofollow">https:&#x2F;&#x2F;developer.chrome.com&#x2F;docs&#x2F;extensions&#x2F;reference&#x2F;decla...</a><p>[3] <a href="https:&#x2F;&#x2F;blog.chromium.org&#x2F;2020&#x2F;12&#x2F;manifest-v3-now-available-on-m88-beta.html" rel="nofollow">https:&#x2F;&#x2F;blog.chromium.org&#x2F;2020&#x2F;12&#x2F;manifest-v3-now-available-...</a>