Google has even been working with the developers of AdBlock Plus on ensuring ad blockers continue to work with Chrome’s Manifest V3. One thing Google is strongly emphasizing is that ad blockers are welcomed in the Chrome extension ecosystem, but they’ll now need to use the new declarativeNetRequest API, which is less invasive to privacy. In the time since then, the Chrome team has taken some feedback from the extension developer community about the changes included with Manifest V3. These capabilities offered extensions in-depth information about your web traffic and in Google’s words gave extensions “access to potentially sensitive user data.” When first proposed, Manifest V3 was a source of significant controversy, as it aimed to deprecate the blocking capabilities of the webRequest API, used by ad blockers like uBlock Origin and Ghostery. Being the third version, it’s been dubbed “Manifest V3,” and it’s the first major revision to the spec since Manifest V2 launched in 2012. Nearly two years ago, Google first took the wraps off of the next major revision of Chrome’s extension manifest, a specification for what Chrome extensions can do and how they can do it. During the Chrome Dev Summit, Google has formally included Manifest V3 in Chrome 88 Beta, allowing extension developers to test the changes to ad blocking, performance, and privacy.
0 kommentar(er)
