diff options
| author | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-23 07:12:26 +0000 |
|---|---|---|
| committer | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-23 07:12:26 +0000 |
| commit | c38ba0250a72f17c2b5caed4dc96dcca8db927b2 (patch) | |
| tree | 2b96576c37cb39ef75d2d4f30d69c4cc049527a4 /app | |
| parent | 1c12ae7b1d3af2578e0fa8411bf70e5e627eebfe (diff) | |
| download | chromium_src-c38ba0250a72f17c2b5caed4dc96dcca8db927b2.zip chromium_src-c38ba0250a72f17c2b5caed4dc96dcca8db927b2.tar.gz chromium_src-c38ba0250a72f17c2b5caed4dc96dcca8db927b2.tar.bz2 | |
Make sure the RootView is sized to the correct bounds when the opaque frame is maximized.It seems that now, when an opaque frame is maximized we also need to add the SM_CXSIZEFRAME to the top of the client rect. I don't know why, it's just is.I reworked the way Widget allows subclasses to handle sizing of the RootView... I delegate responsibility for determining the RootView's bounds to a helper virtual function which BrowserFrameWin overrides. This seems cleaner to me. I make sure this handling only occurs when the window is not maximized.http://crbug.com/25227TEST=use to a theme or switch off glass on vista or use Xp. Maximize the browser window. The tabs should be entirely visible.
Review URL: http://codereview.chromium.org/304007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29882 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'app')
| -rw-r--r-- | app/gfx/insets.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/app/gfx/insets.h b/app/gfx/insets.h index 6a4ac05..6b8e9b1 100644 --- a/app/gfx/insets.h +++ b/app/gfx/insets.h @@ -33,6 +33,9 @@ class Insets { // top and bottom insets. int height() const { return top_ + bottom_; } + // Returns true if the insets are empty. + bool empty() const { return width() == 0 && height() == 0; } + void Set(int top, int left, int bottom, int right) { top_ = top; left_ = left; |