Comment #14 on issue 29621 by megazzt: Content scripts not injected in extension processes http://code.google.com/p/chromium/issues/detail?id=29621
You can see this issue in my extension One Number 1.0/1.1, where I was opening new tabs incorrectly with window.open, which caused the new tabs to be opened in the extension's process (hmm maybe this should be filed as a separate bug.). Users reported extensions not working in these tabs. I figured it was "by design" and not a bug since extensions shouldn't really be able to mess with other extensions I think? Anyways don't bother checking it out in 1.2 since I use the proper chrome.tabs.create APIs now. Not sure if the gallery keeps copies of old versions? -- 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
