Plumb native AppWindow input region through to window shape under Aura.

chrome/browser/ui/views/apps/native_app_window_views.cc

Index: chrome/browser/ui/views/apps/native_app_window_views.cc
diff --git a/chrome/browser/ui/views/apps/native_app_window_views.cc b/chrome/browser/ui/views/apps/native_app_window_views.cc
index 42a543b0a8b66321e456cfe772163b26465d8f38..13709194ebb4148b04ac61ec3aba21bfa2f19d11 100644
--- a/chrome/browser/ui/views/apps/native_app_window_views.cc
+++ b/chrome/browser/ui/views/apps/native_app_window_views.cc
@@ -807,6 +807,13 @@ SkRegion* NativeAppWindowViews::GetDraggableRegion() {
 
 void NativeAppWindowViews::UpdateInputRegion(scoped_ptr<SkRegion> region) {
   input_region_ = region.Pass();
+
+#if defined(USE_AURA)

[Ben Goodger (Google), 2013/11/01 16:39:47]

is there a reason this has to be USE_AURA? It should work on non-Aura too?

[Wez, 2013/11/01 19:59:33]

UpdateInputRegion() takes scoped_ptr<SkRegion>, while SetShape() takes
gfx::NativeRegion. We will re-name UpdateInputRegion to SetWindowShape(), and we
can change the signature at the same time.

Alternatively, I can add the SkRegion->NativeRegion conversion here, for now -
let me know which you prefer.

+  if (input_region_)
+    window_->SetShape(new SkRegion(*input_region_));
+  else
+    window_->SetShape(NULL);
+#endif // defined(USE_AURA)
 }
 
 void NativeAppWindowViews::HandleKeyboardEvent(