third_party: Amend version 3 of remote shell protocol

third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml

 <?xml version="1.0" encoding="UTF-8"?>
 <protocol name="remote_shell_unstable_v1">
 
   <copyright>
     Copyright 2016 The Chromium Authors.
 
     Permission is hereby granted, free of charge, to any person obtaining a
     copy of this software and associated documentation files (the "Software"),
     to deal in the Software without restriction, including without limitation
     the rights to use, copy, modify, merge, publish, distribute, sublicense,
@@ skipping 46 matching lines @@
     <enum name="state_type">
       <description summary="state types for remote surfaces">
         Defines common show states for shell surfaces.
       </description>
       <entry name="normal" value="1" summary="normal window state"/>
       <entry name="minimized" value="2" summary="minimized window state"/>
       <entry name="maximized" value="3" summary="maximized window state"/>
       <entry name="fullscreen" value="4" summary="fullscreen window state"/>
       <entry name="pinned" value="5" summary="pinned window state"/>
       <entry name="trusted_pinned" value="6" summary="trusted pinned window state"/>
+      <entry name="moving" value="7" summary="moving window state"/>
     </enum>
 
     <enum name="error">
       <entry name="role" value="0" summary="given wl_surface has another role"/>
       <entry name="invalid_notification_id" value="1"
        summary="invalid notification id"/>
     </enum>
 
     <enum name="layout_mode">
       <description summary="the layout mode">
@@ skipping 285 matching lines @@
         if your application has any...
 
         This is only a request that the user intends to close your
         window. The client may choose to ignore this request, or show
         a dialog to ask the user to save their data...
       </description>
     </event>
 
     <event name="state_type_changed">
       <description summary="surface state type changed">
-        The state_type_changed event is sent by the compositor when the surface
-        state changed.
+        [Deprecated] The state_type_changed event is sent by the compositor when
+        the surface state changed.
 
         This is an event to notify that the window state changed in compositor.
         The state change may be triggered by a client's request, or some user
         action directly handled by the compositor. The client may choose to
         ignore this event.
       </description>
       <arg name="state_type" type="uint"/>
     </event>
 
     <!-- Version 2 additions -->
@@ skipping 19 matching lines @@
 
     <event name="configure" since="3">
       <description summary="suggest a surface change">
         The configure event asks the client to change surface state.
 
         The origin arguments specify the position, in the compositor coordinate
         space, of the virtual display used by the client to simulate multiple
         displays. The client must offset window positions in set_window_geometry
         requests by this origin in order to convert between coordinate spaces.
 
+        The states listed in the event are state_type values, and might change
+        due to a client request or an event directly handled by the compositor.
+
         Clients should arrange their surface for the new state, and then send an
         ack_configure request with the serial sent in this configure event at
         some point before committing the new surface.
 
         If the client receives multiple configure events before it can respond
         to one, it is free to discard all but the last event it received.
       </description>
       <arg name="origin_x" type="int"/>
       <arg name="origin_y" type="int"/>
+      <arg name="states" type="array"/>
       <arg name="serial" type="uint"/>
     </event>
 
     <request name="ack_configure" since="3">
       <description summary="ack a configure event">
         When a configure event is received, if a client commits the
         surface in response to the configure event, then the client
         must make an ack_configure request sometime before the commit
         request, passing along the serial of the configure event.
 
         For instance, the compositor might use this information during display
         configuration to change its coordinate space for set_window_geometry
         requests only when the client has switched to the new coordinate space.
 
         If the client receives multiple configure events before it
         can respond to one, it only has to ack the last configure event.
 
         A client is not required to commit immediately after sending
         an ack_configure request - it may even ack_configure several times
         before its next surface commit.
 
         A client may send multiple ack_configure requests before committing, but
         only the last request sent before a commit indicates which configure
         event the client really is responding to.
       </description>
       <arg name="serial" type="uint" summary="the serial from the configure event"/>
     </request>
 
-    <request name="set_moving" since="3">
-      <description summary="interactive move started">
-        Notifies the compositor when an interactive, user-driven move of the
-        surface starts. The compositor may assume that subsequent
-        set_window_geometry requests are position updates until it receives a
-        unset_moving request.
+    <request name="move" since="3">
+      <description summary="start an interactive move">
+        Start an interactive, user-driven move of the surface.
+
+        The compositor responds to this request with a configure event that
+        transitions to the "moving" state. The client must only initiate motion
+        after acknowledging the state change. The compositor can assume that
+        subsequent set_window_geometry requests are position updates until the
+        next state transition is acknowledged.
+
+        The compositor may ignore move requests depending on the state of the
+        surface, e.g. fullscreen or maximized.
       </description>
     </request>
 
-    <request name="unset_moving" since="3">
-      <description summary="interactive move stopped">
-        Notifies the compositor when an interactive, user-driven move of the
-        surface stops. The compositor may choose to stop the move regardless
-        of this request.
-      </description>
-    </request>
-
   </interface>
 
   <interface name="zcr_notification_surface_v1" version="1">
     <description summary="A notification window">
       An interface that may be implemented by a wl_surface to host
       notification contents.
     </description>
 
     <request name="destroy" type="destructor">
       <description summary="Destroy the notification_surface">
         Unmap and destroy the notification surface.
       </description>
     </request>
   </interface>
 
 </protocol>