summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser.h
diff options
context:
space:
mode:
authormad@chromium.org <mad@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-12 14:46:17 +0000
committermad@chromium.org <mad@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-12 14:46:17 +0000
commitf21c613a0ab52b707f8a2effacda74c77f4448ea (patch)
tree09051d286db764a71b97bc01f35765e607b4d20f /chrome/browser/browser.h
parent822cfc93fe52974b904b7f184c5448dee5d281c5 (diff)
downloadchromium_src-f21c613a0ab52b707f8a2effacda74c77f4448ea.zip
chromium_src-f21c613a0ab52b707f8a2effacda74c77f4448ea.tar.gz
chromium_src-f21c613a0ab52b707f8a2effacda74c77f4448ea.tar.bz2
This is an attempt at finding the reason for the page_cycler slowness caused by
the new resize corner. Local experiment led me to believe that it is WebKit that is slower when we specify a resize corner area. To validate this hypothesis, I always return an empty rect to WebKit, but I still compute and push the rect to the render widget and I also draw the bitmap even if this will cause it to be drawn on top of the scroll bars when there is only one. TBR=brettw git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9654 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser.h')
-rw-r--r--chrome/browser/browser.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/browser/browser.h b/chrome/browser/browser.h
index ea9a57d..858d5c4 100644
--- a/chrome/browser/browser.h
+++ b/chrome/browser/browser.h
@@ -391,6 +391,7 @@ class Browser : public TabStripModelDelegate,
virtual void BeforeUnloadFired(TabContents* source,
bool proceed,
bool* proceed_to_fire_unload);
+ virtual gfx::Rect GetRootWindowResizerRect() const;
virtual void ShowHtmlDialog(HtmlDialogContentsDelegate* delegate,
void* parent_window);
virtual void SetFocusToLocationBar();