Comment #4 on issue 12306 by [email protected]: Extensions: various issues around NPAPI loading and unloading http://code.google.com/p/chromium/issues/detail?id=12306
(b) and (c) can be mostly solved by the ViewMsg_PurgePluginListCache message - it notifies the renderer to rebuild its plugin list. I don't know what will happen if the plugin is in use by a page, though. (a) is more complicated. Options: - wait until all NPAPI-carrying extensions are loaded before starting renderers - let renderers start, but send the Purge message when extensions are loaded. Currently Purge doesn't reload the page, but we can make it an optional, in which case it would reload any page that has plugins. This might be weird and destructive. - do nothing, until we refactor so manifests are in the Prefs file. Then it might be fast enough to not have a race. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
