Call OnNativeWindowChanged after maximizing and restoring.

ui/views/widget/native_widget_aura.cc

Index: ui/views/widget/native_widget_aura.cc
diff --git a/ui/views/widget/native_widget_aura.cc b/ui/views/widget/native_widget_aura.cc
index e57a4ff0bc0ecb56c12fba415058f0d60a13b85f..0aba3dce6759e431036b452bdafbcb75e56c7dde 100644
--- a/ui/views/widget/native_widget_aura.cc
+++ b/ui/views/widget/native_widget_aura.cc
@@ -738,6 +738,13 @@ void NativeWidgetAura::OnBoundsChanged(const gfx::Rect& old_bounds,
     delegate_->OnNativeWidgetSizeChanged(new_bounds.size());
 }
 
+void NativeWidgetAura::OnPropertyChanged(const void* key, intptr_t old) {
+  if (key == aura::client::kShowStateKey) {
+    delegate_->OnNativeWidgetWindowShowStateChanged(

[sky, 2014/08/06 17:23:00]

Won't this result in double the notifications if the bounds do change? Also,
might this be invoked before the bounds have changed? That said, I can't think
of a better way to handle this without adding something on
OnAfterPropertyChanged, which I'm loathe to suggest right now.

[jackhou1, 2014/08/11 05:41:06]

Yeah, SaveWindowPlacement gets called twice. I think the expensive part is
writing to prefs. I don't have any better ideas on how to avoid it though =S.

The bounds are correct in the JS context, so I assume it's being called after
the bounds change, unless there's an asynchronous step.

+        static_cast<ui::WindowShowState>(old));
+  }
+}
+
 gfx::NativeCursor NativeWidgetAura::GetCursor(const gfx::Point& point) {
   return cursor_;
 }