I landed the patch, and now the code in browser/privacy_blacklist should be
quite stable (at least the interfaces).
There's still a lot of work to do, but here's my plan for now:
- make ExtensionsService a BlacklistPathProvider and write a test which
loads an extension and verifies that BlacklistManager notices that (I'm
working on it now)
- verify that blacklists are valid (the format is correct) when validating
an extension (and update unit tests)
- use BlacklistManager in ChromeURLRequestContext, pausing requests until
the blacklist has loaded and write an integration test
On Mon, Oct 26, 2009 at 09:05, Paweł Hajdan Jr. <phajdan...@chromium.org>wrote:
> Please don't make non-trivial changes to chrome/browser/privacy_blacklists
> if possible. I have a big change which I'll be soon (today) submitting for
> review. It will be needed to integrate privacy blacklists with extensions.
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
