Comment #30 on issue 2993 by ecroyd: Tab is dragged from window even after mouse is released http://code.google.com/p/chromium/issues/detail?id=2993
If this problem was too hard to fix and a work around needed, I think an auto detecting work around would be better than providing an option to "never undock". I do not think that such a solution would be hard. After the mouse is released and before the tab undocks, chrome could check the CPU usage. As this problem only seems to occur on high CPU usage, chrome could stop tabs being undocked while the CPU is being heavily used. (Or chrome could require the mouse button to be held down longer when CPU is heavily used.) -- 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 -~----------~----~----~----~------~----~------~--~---
