Minimize resize calls

views/controls/native/native_view_host.cc

Index: views/controls/native/native_view_host.cc
diff --git a/views/controls/native/native_view_host.cc b/views/controls/native/native_view_host.cc
index 728f70c8e0bee763169a20f57b4cb69d551d7693..2238e9946a6cb4fa79941eadf39812f9fe96287b 100644
--- a/views/controls/native/native_view_host.cc
+++ b/views/controls/native/native_view_host.cc
@@ -152,7 +152,11 @@ bool NativeViewHost::NeedsNotificationWhenVisibleBoundsChange() const {
   // The native widget is placed relative to the root. As such, we need to
   // know when the position of any ancestor changes, or our visibility relative
   // to other views changed as it'll effect our position relative to the root.
+#if !defined(USE_AURA)
   return true;
+#else
+  return false;

[sky, 2011/10/27 14:40:47]

This comment seems to apply to aura. Why do we want to return false here?

[DaveMoore, 2011/10/27 21:25:13]

Do we need this when there's only one native window to host everything? What I
saw was that this gets triggered by the bounds change and then it causes us to
do another layout. I saw no downside on the device when I changed this.

On 2011/10/27 14:40:47, sky wrote:

[sky, 2011/10/27 22:12:20]

We still have child windows for the TabContents and RWHV. If we had a situation
where the position in the parent changed but the bounds didn't, then we would
want this code.
Shouldn't it result in a no-op because we invoke SetBounds with the same bounds,
which because of your change to Window does nothing?

[DaveMoore, 2011/10/28 16:46:48]

Done.

+#endif
 }
 
 void NativeViewHost::OnVisibleBoundsChanged() {