Fix BrowserFrameWin artifact on opaque to glass frame changes.
The problem when switching from an opaque frame to a glass frame:
Calling UpdateDWMFrame() first uses stale glass inset values.
(from the old OpaqueBrowserFrameView's tabstrip bounds, yielding 45px on top)
HandleFrameChanged() then sets the new GlassBrowserFrameView with a larger top inset.
(but doesn't update the dwm glass inset until the next UpdateDWMFrame, for 49px on top)
Swapping the call order works without any apparent regressions.
(this puts the new frame in place before updating the dwm glass insets)
See http://crrev.com/29164 for a contradictory change that may be outdated.
Also, use the more convenient IsFullscreen() call, no behavior change.
BUG=156982
TEST=No black bar switching from theme->glass chrome on Windows; no regressions.
R=ben@chromium.org
Review URL: https://codereview.chromium.org/11273107
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165265 0039d316-1c4b-4281-b951-d872f2087c98
1 file changed
