Comment #28 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

The following revision refers to this bug:
     http://src.chromium.org/viewvc/chrome?view=rev&revision=33297

------------------------------------------------------------------------
r33297 | [email protected] | 2009-11-30 09:45:03 -0800 (Mon, 30 Nov  
2009) | 17 lines
Changed paths:
    M  
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/cocoa/chrome_event_processing_window.mm?r1=33297&r2=33296
    M  
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/cocoa/status_bubble_mac.h?r1=33297&r2=33296
    M  
http://src.chromium.org/viewvc/chrome/branches/249/src/chrome/browser/cocoa/status_bubble_mac.mm?r1=33297&r2=33296

Merge 33287 - Mac: improve apparent zorder problems when switching Spaces.

Remove the status bubble as child window when hidden, rather than just  
setting
its opacity to 0. I'm not sure about the effects, if any, of doing this  
rather
than destroying the window completely. This doesn't eliminate zorder  
problems
with Spaces, but should improve it considerably.

This may also ameliorate the problems with moving windows between Spaces  
using
Expose.

BUG=28107, 24956
TEST=Create a bunch of windows; get the status bubble to appear in the  
active (key) window and then get it to disappear; switch to another spaces  
and back; make sure the active window is on top; repeat.

Review URL: http://codereview.chromium.org/434120

[email protected], [email protected], [email protected]
Review URL: http://codereview.chromium.org/457001
------------------------------------------------------------------------


--
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

Reply via email to