summaryrefslogtreecommitdiffstats
path: root/chrome/views/views.vcproj
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/views/views.vcproj
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/views/views.vcproj')
-rw-r--r--chrome/views/views.vcproj8
1 files changed, 0 insertions, 8 deletions
diff --git a/chrome/views/views.vcproj b/chrome/views/views.vcproj
index 6d5ce3d..9656303 100644
--- a/chrome/views/views.vcproj
+++ b/chrome/views/views.vcproj
@@ -466,14 +466,6 @@
>
</File>
<File
- RelativePath=".\resize_corner.cc"
- >
- </File>
- <File
- RelativePath=".\resize_corner.h"
- >
- </File>
- <File
RelativePath=".\root_view.cc"
>
</File>