Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 21921 by [email protected]: Incorrect WM_NCCALCSIZE handling breaks
compositing after toggling Aero on/off
http://code.google.com/p/chromium/issues/detail?id=21921
Chrome Version : Chromium 4.0.206.0 (25232) (development build)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4:
Firefox 3.x:
IE 7:
IE 8:
WindowWin::FrameTypeChanged() (src/views/window/window_win.cc) currently
calls GetWindowPlacement() / Hide() / SetWindowPlacement() to work around a
bug (http://crbug.com/14578) where turning Aero off and then back on causes
the border of the Chrome window to turn black rather than allow the glass
effect to show through.
Unfortunately the hiding and showing of the browser window is causing O3D's
full-screen support to break. O3D uses Direct3D to go into full-screen mode
on Windows, which turns off the compositing engine. The browser window
grabs the activation very soon after O3D goes full-screen and Direct3D
subsequently tears down the full-screen window.
After investigation and discussion with [email protected] and
[email protected] we have determined that the black border is appearing
because of incorrect computation in the WM_NCCALCSIZE handler in the
BrowserFrameWin class. Diffs are attached which seem to make the
compositing work correctly after toggling Aero on/off without the
GetWindowPlacement / SetWindowPlacement hack.
What steps will reproduce the problem?
1. Comment out the code in WindowWin::FrameTypeChanged() which calls
GetWindowPlacement / SetWindowPlacement.
2. Use the Appearance Settings Control Panel to turn off Aero and then turn
it back on.
What is the expected result?
The Chrome window should be rendered with the glass effect behind the tabs.
What happens instead?
The Chrome window is rendered with a black border behind the tabs and the
renderer's output.
Please provide any additional information below. Attach a screenshot if
possible.
Attachments:
compositing-issue.txt 1.7 KB
--
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
-~----------~----~----~----~------~----~------~--~---
