Draggable region support for frameless app window on Windows.

content/common/view_messages.h

Index: content/common/view_messages.h
diff --git a/content/common/view_messages.h b/content/common/view_messages.h
index a1d3c73f8c1b7b7ec15105a08ffadcf992be84c7..965713e9c56eb6996cf3ba7a57bb6d55bdb79726 100644
--- a/content/common/view_messages.h
+++ b/content/common/view_messages.h
@@ -14,6 +14,7 @@
 #include "content/common/view_message_enums.h"
 #include "content/public/common/common_param_traits.h"
 #include "content/public/common/context_menu_params.h"
+#include "content/public/common/draggable_region.h"
 #include "content/public/common/file_chooser_params.h"
 #include "content/public/common/frame_navigate_params.h"
 #include "content/public/common/javascript_message_type.h"
@@ -2185,3 +2186,7 @@ IPC_MESSAGE_ROUTED3(ViewHostMsg_PepperPluginHung,
 // Screen was rotated. Dispatched to the onorientationchange javascript API.
 IPC_MESSAGE_ROUTED1(ViewMsg_OrientationChangeEvent,
                     int /* orientation */)
+
+// Sent to the browser to update the draggable regions
+IPC_MESSAGE_ROUTED1(ViewHostMsg_UpdateDraggableRegions,
+                    std::vector<content::DraggableRegion> /* regions */)

[jeremya, 2012/08/07 01:00:17]

I talked with jamesr a while ago about the best way to do this, and he suggested
maybe sending the draggable region data along with the UpdateRect message (which
include among other things plugin window move information). I think doing it
that way would guarantee that the draggable regions would always be in sync with
the pixels.

This way is fine for now, but it might be good to think about merging this
message with UpdateRect :)