7 votes

Web Request and Declarative Net Request: Explaining the impact on Extensions in Manifest V3

1 comment

  1. Wes Link
    I know this topic has been done to death, but this is Google's official response to the criticisms of Manifest v3. They've also made some adjustments based on feedback to the API. This addresses a...

    I know this topic has been done to death, but this is Google's official response to the criticisms of Manifest v3. They've also made some adjustments based on feedback to the API.

    Since the original announcement of the Declarative Net Request API, we have added significant functionality to the API as a result of these discussions. The Declarative Net Request API now allows for the registration and removal of dynamic rules - specified at runtime rather than statically in the manifest. We’ve also added the capability to remove common tracking headers, such as Referer, Cookie, and Set-Cookie.

    We are actively exploring other ways to expand this API, including adding methods to get feedback about matched rules, and support for richer redirects leveraging URL manipulation and regular expressions. Additionally, we are currently planning to change the rule limit from maximum of 30k rules per extension to a global maximum of 150k rules.

    This addresses a number of the concerns that were raised about losing functionality over netRequest.

    I won't post it as a separate submission, but they also posted to the Security blog with a simpler explanation of events.

    https://security.googleblog.com/2019/06/improving-security-and-privacy-for.html

    3 votes