"Google announced MV3 back in 2019 when it had become apparent that the powerful capabilities exposed to extension developers through MV2 could be (and were) easily abused. The company's answer involved a revised set of APIs that limited those capabilities and revised the underlying architecture to improve performance. The most widely noted of those APIs was the blocking ( synchronous) version of chrome.webRequest."
"Under MV2, it could intercept and modify incoming network data, making it ideal for stopping ads, tracking scripts, and making other interventions. MV3 stopped supporting the blocking version of chrome.webRequest and replaced it with chrome.declarativeNetRequest. The new API is asynchronous (capable of concurrent task processing) rather than synchronous (processes tasks in sequence), which has performance benefits but is less flexible in terms of adapting to page content on the fly."
Comparisons of Manifest V3 (MV3) and Manifest V2 (MV2) implementations show no statistically significant reduction in ad-blocking or anti-tracking effectiveness; some MV3 instances show slight improvements in blocking trackers. MV3 removed the blocking (synchronous) chrome.webRequest API and introduced chrome.declarativeNetRequest, an asynchronous API that improves performance but limits real-time adaptability to page content. MV2's blocking webRequest could intercept and modify network data, facilitating the stopping of ads and tracking scripts. Revisions to APIs and architecture aimed to curb abuse of MV2 capabilities while improving performance. Concerns about these changes alarmed content-blocking and privacy-extension makers.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]