diff options
| author | jamescook@chromium.org <jamescook@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-09 20:53:59 +0000 |
|---|---|---|
| committer | jamescook@chromium.org <jamescook@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-09 20:53:59 +0000 |
| commit | 970451967309a8ab26faaa370fa54ffccec70e24 (patch) | |
| tree | 59682eadf710b65237fbc8b01647bcd227371fd8 /ash/shell | |
| parent | 3f01c469931174046154274c10838f19492efe9d (diff) | |
| download | chromium_src-970451967309a8ab26faaa370fa54ffccec70e24.zip chromium_src-970451967309a8ab26faaa370fa54ffccec70e24.tar.gz chromium_src-970451967309a8ab26faaa370fa54ffccec70e24.tar.bz2 | |
Ash: Correctly initialize transparency flag for windows
Widgets of TYPE_WINDOW have potentially transparent frames on Ash. I was initializing the transparency flag in the wrong place, leading to a subset of dialogs (edit bookmark, app shortcut, restart chrome, etc.) having black pixels at their outside corners and the wrong appearance in the inactive state. Inspection of the Widget::CreateWindow* callers suggests this is the right place to put this.
BUG=117411
TEST=visual inspection of bookmark windows
Review URL: https://chromiumcodereview.appspot.com/9653011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@125894 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash/shell')
| -rw-r--r-- | ash/shell/shell_main.cc | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/ash/shell/shell_main.cc b/ash/shell/shell_main.cc index c1c6d83..339010b 100644 --- a/ash/shell/shell_main.cc +++ b/ash/shell/shell_main.cc @@ -45,6 +45,10 @@ class ShellViewsDelegate : public views::TestViewsDelegate { views::Widget* widget) OVERRIDE { return ash::Shell::GetInstance()->CreateDefaultNonClientFrameView(widget); } + bool UseTransparentWindows() const OVERRIDE { + // Ash uses transparent window frames. + return true; + } private: DISALLOW_COPY_AND_ASSIGN(ShellViewsDelegate); |