Comment #23 on issue 24956 by [email protected]: Chrome no longer allows windows to be in separate spaces http://code.google.com/p/chromium/issues/detail?id=24956
My current feeling is that status bubbles are the cause of issue 28107 (it makes so much sense), but are merely related to this issue. In particular, when dealing with Spaces/Exposé, I tend to the following disturbingly often: [5540:267:366203172653352:FATAL:/[...]/src/chrome/browser/cocoa/chrome_even t_processing_window.mm(72)] Check failed: [event window] == self (0x1ffd1be0 vs. 0x163db0) The problem with the interim fix I mention above is that it's extremely easy to press F8 with a status bubble showing (the fix works much better in countering the z-order bug). -- 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
