Chrome is right to remove the webRequest extension API

The replacement API gives extension developers much of the same capabilities, but moves evaluation of the network requests out of the extension’s JavaScript and into the browser engine itself. None of my own extensions that use the API today could be re-implemented using the proposed API, despite most of their usage of the API center around redirecting requests using simple dynamic redirect rules. The API is also terrible to work with as developers can’t even use their browser’s own developer tools to inspect all the changes that their extensions are capable of making to a request.

Source: www.ctrl.blog