diff options
author | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-01 22:44:56 +0000 |
---|---|---|
committer | estade@chromium.org <estade@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-05-01 22:44:56 +0000 |
commit | 36c165e203d4ddf415c29b865b4c13f0b9f32d38 (patch) | |
tree | 7d6b208cf21fa0cfd326d25a873857f25504555c /webkit/tools/test_shell/test_webview_delegate.h | |
parent | 5f594c011f9da68070a44cf3a97b411efa90d7c3 (diff) | |
download | chromium_src-36c165e203d4ddf415c29b865b4c13f0b9f32d38.zip chromium_src-36c165e203d4ddf415c29b865b4c13f0b9f32d38.tar.gz chromium_src-36c165e203d4ddf415c29b865b4c13f0b9f32d38.tar.bz2 |
Make the findbar slide in/out.
Change SlideAnimatorGtk so that its GtkFixed doesn't have its own window. Giving that fixed its own GdkWindow meant that as a client of SlideAnimatorGtk you were pretty much cornered into having rectangular widgets (unless you want to perform a lot of expensive operations during every frame of the slide). We solve the clipping problem this creates by making a "render area" vbox in BrowserWindowGtk that is all part of a single GdkWindow hierarchy.
This isn't yet perfect as there are sometimes occlusion problems with infobars. That will probably need to be solved in the same way it was solved for the tab contents container. This patch is already hard enough to grok, so I'm going to leave that problem for another patch.
Review URL: http://codereview.chromium.org/102021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15112 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/tools/test_shell/test_webview_delegate.h')
0 files changed, 0 insertions, 0 deletions