5 ms·
The main dev on the WebRequest API sits right behind me, and is making steady progress. It's the first synchronous extension API that interacts with the network
by mikewest 15y ago
The main dev on the WebRequest API sits right behind me, and is making steady progress. It's the first synchronous extension API that interacts with the network stack, and it's a nontrivial effort to get it running. I can assure you, however, that making life hard for privacy extensions is the exact opposite of what we're being paid to do.
Look at the progress on privacy-related APIs over the last year: WebRequest is coming along nicely, WebNavigation and ContentSettings are feature complete and in the final stages of polish, and Proxy went out to stable in Chrome 13. Privacy and Clear just landed in experimental, and we're iterating on them rapidly.
(Details on the state of each are available at http://code.google.com/chrome/extensions/trunk/experimental.html http://code.google.com/chrome/extensions/trunk/experimental....)
- qjz 15y agoIs it possible to restrict requests to the host in the URL I'm visiting? XSS, DNT, etc. become much less of an issue when you can block all external resources requested by a page.
- mikewest 15y agoThat will be possible with the WebRequest API, yes: http://code.google.com/chrome/extensions/trunk/experimental.webRequest.html http://code.google.com/chrome/extensions/trunk/experimental.... For example, you'd be able to intercept and block network requests from a particular tab that didn't hit the same domain. The API in experimental now, so download a dev release of Chrome/Chromium, enable experimental APIs via `about:flags`, and start filing bug reports. :)
- mike-cardwell 15y agoFWIW, this is already possible with Firefox by using the RequestPolicy addon.
- notbitter 15y agoGlad to hear it. Chrome is great in every other way.