16 ms·
The existing webRequest API lets extensions run arbitrary third-party code over all the requests you make, and Chrome won't process the request until it's done.
by SpicyLemonZest 7y ago
The existing webRequest API lets extensions run arbitrary third-party code over all the requests you make, and Chrome won't process the request until it's done. That inevitably means that a badly written extension can hurt page loading performance, and a malicious extension can get a lot of sensitive data about you.
Whatever Google's true motivation is, there's no way to solve those problems without limiting the power available to ad blockers.
- the8472 7y agoThe performance concern can be addressed by monitoring it and informing the user when extensions slow down page loads. The security concern is difficult to solve (more fine-grained permissions might help), but also seems a bit disingenuous since extensions can also inject code into the HTML of all sites and already syphon off a lot of data if they want to. Sure, it's a sharp knife, but some tough issues require sharp tools.