Comment #7 on issue 11402 by blackboxxx: click on an item in context menu doesn't work when Chrome unresponsive http://code.google.com/p/chromium/issues/detail?id=11402
I can reproduce this issue running 4.0.221.6 (Official Build 28091). Restarting Chrome (especially after cold boot) with about 30 tabs saved in the last session causes ALL Chrome menus (drop-down and context) to be unresponsive to clicking until everything settles down and CPU usage drops. What's particularly annoying is that the menus themselves are displayed immediately after right-clicking or clicking drop-down buttons, so it's not that there are no CPU resources to respond to the menu selection. In fact, I'd prefer if Chrome didn't display any menu until it was able to respond properly, otherwise it just tends to confuse the user. I think this bug should be given a higher priority because for a browser that prides itself as the fastest this issue is simply inexcusable. -- 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 -~----------~----~----~----~------~----~------~--~---
