Status: Unconfirmed Owner: [email protected] Labels: OS-Linux Area-Extensions Type-Bug Pri-3
New issue 24584 by [email protected]: chrome.tabs.onCreated.addListener can make the inspector unusable? http://code.google.com/p/chromium/issues/detail?id=24584 I found that chrome.tabs.onCreated.addListener can make the DOM inspector unusable. I'm not certain it's really a bug, though. Chrome Version : ToT, 4.0.222.4 (Developer Build 28662), Release build OS + version : Ubuntu Janunty CPU architecture (32-bit / 64-bit): 32 window manager : GNOME default Behavior in Chrome for Windows (optional): not checked yet. not sure if it's a cross-platform issue. What steps will reproduce the problem? 1. Write an extension (background_page) like: <html><head> <script type="text/javascript"> function init() { chrome.tabs.onCreated.addListener(function(tab) { chrome.tabs.update(tab.id, { "url": "http://www.google.com/"; }); }); } </script></head> <body onLoad="javascript:init()"></body> </html> 2. Visit the chrome://extensions page and load the unpacked extension above. 3. Press Ctrl-t and visit the new-tab-page. 4. Press Shift-Ctrl-j to show the inspector window. What is the expected result? The inspector window is shown. What happens instead? Two or three inspector windows are repeatedly created and destroyed. The inspector is entirely unusable. Please provide any additional information below. Attach a screenshot and backtrace if possible. Probably we should not call onCreated functions upon Shift+Ctrl+j? -- 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 -~----------~----~----~----~------~----~------~--~---
