I agree the background page should load first. What's happening right now is that ExtensionProcessManager monitors EXTENSIONS_LOADED, just like everyone else (including Browser) so they get loaded about the same time. It looks like currently the background page starts first, because it was registered first, but it's basically a race.
- a 2009/6/10 Nick Baum <[email protected]>: > This might be the same problem I ran into when writing my extension: because > the bg page and toolstrips don't load in a predictable order, you're not > guaranteed to catch all views if you do getViews() right as the page loads. > If the background page was guaranteed to load first, the toolstrips could > all make sure to find it when they loaded. > -Nick > > 2009/6/10 Aaron Boodman <[email protected]> >> >> On Wed, Jun 10, 2009 at 3:17 PM, Nebojša Ćirić<[email protected]> wrote: >> > What about the second issue? Shouldn't iterating over background page >> > views >> > return toolstrip views, instead of background page itself (and no >> > toolstrip >> > views)? I'll try it again just to make sure I didn't make an obvious >> > mistake... >> >> This method should return all running HTML pages in your extension -- >> this includes the background page, any toolstrips, and any tabs that >> are showing HTML from the extension. If it's not doing that, it's a >> bug. >> >> - a >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
