On Thu, Oct 29, 2009 at 21:50, Paweł Hajdan Jr. <[email protected]>wrote:
> - make ExtensionsService a BlacklistPathProvider and write a test which > loads an extension and verifies that BlacklistManager notices that (I'm > working on it now) > This is done. To clarify: you can't yet load an extension in the browser and see the effects of the blacklist. The test I wrote so far is using BlacklistManager manually. The "full scenario" will be available only after integrating BM with Profile and ChromeURLRequestContext. I'm now fixing some threading issues in BlacklistManager (switching to ChromeThread), and then will continue with the rest: > - 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 > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
