summaryrefslogtreecommitdiffstats
path: root/chrome/browser/browser.cc
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.cc
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.cc')
-rw-r--r--chrome/browser/browser.cc8
1 files changed, 6 insertions, 2 deletions
diff --git a/chrome/browser/browser.cc b/chrome/browser/browser.cc
index da7804f..3e5ae22 100644
--- a/chrome/browser/browser.cc
+++ b/chrome/browser/browser.cc
@@ -1082,7 +1082,7 @@ void Browser::ExecuteCommand(int id) {
case IDC_NEW_WINDOW_PROFILE_5:
case IDC_NEW_WINDOW_PROFILE_6:
case IDC_NEW_WINDOW_PROFILE_7:
- case IDC_NEW_WINDOW_PROFILE_8:
+ case IDC_NEW_WINDOW_PROFILE_8:
NewProfileWindowByIndex(id - IDC_NEW_WINDOW_PROFILE_0); break;
#if defined(OS_WIN)
case IDC_CLOSE_WINDOW: CloseWindow(); break;
@@ -1365,7 +1365,7 @@ bool Browser::RunUnloadListenerBeforeClosing(TabContents* contents) {
if (web_contents) {
// If the WebContents is not connected yet, then there's no unload
// handler we can fire even if the WebContents has an unload listener.
- // One case where we hit this is in a tab that has an infinite loop
+ // One case where we hit this is in a tab that has an infinite loop
// before load.
if (TabHasUnloadListener(contents)) {
// If the page has unload listeners, then we tell the renderer to fire
@@ -1839,6 +1839,10 @@ void Browser::BeforeUnloadFired(TabContents* tab,
*proceed_to_fire_unload = true;
}
+gfx::Rect Browser::GetRootWindowResizerRect() const {
+ return window_->GetRootWindowResizerRect();
+}
+
void Browser::ShowHtmlDialog(HtmlDialogContentsDelegate* delegate,
void* parent_window) {
window_->ShowHTMLDialog(delegate, parent_window);