Use pixel coordinates for shadow underlay bounds

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

Index: third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml
diff --git a/third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml b/third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml
index 89d3e97c22acf152f712301aca8828cdea0429ef..2e5d974ddae0bc249432759bb1e544bad5918ecf 100644
--- a/third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml
+++ b/third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml
@@ -38,7 +38,7 @@
     reset.
   </description>
 
-  <interface name="zcr_remote_shell_v1" version="2">
+  <interface name="zcr_remote_shell_v1" version="3">
     <description summary="remote_shell">
       The global interface that allows clients to turn a wl_surface into a
       "real window" which is remotely managed but can be stacked, activated
@@ -140,7 +140,7 @@
     </event>
   </interface>
 
-  <interface name="zcr_remote_surface_v1" version="2">
+  <interface name="zcr_remote_surface_v1" version="3">
     <description summary="A desktop window">
       An interface that may be implemented by a wl_surface, for
       implementations that provide a desktop-style user interface
@@ -207,7 +207,7 @@
 
     <request name="set_rectangular_shadow">
       <description summary="set a rectangular shadow">
-	Request that surface needs a rectangular shadow.
+	[Deprecated] Request that surface needs a rectangular shadow.
 
 	This is only a request that the surface should have a rectangular
 	shadow. The compositor may choose to ignore this request.
@@ -382,7 +382,72 @@
 
     <!-- Version 2 additions -->
 
-    <request name="set_moving" since="2">
+    <request name="set_rectangular_surface_shadow" since="2">
+      <description summary="set a rectangular shadow">
+	Request that surface needs a rectangular shadow.
+
+	This is only a request that the surface should have a rectangular
+	shadow. The compositor may choose to ignore this request.
+
+	The arguments are given in the remote surface coordinate space and
+	specifies inner bounds of the shadow. Specifying zero width and height
+	will disable the shadow.
+      </description>
+      <arg name="x" type="int"/>
+      <arg name="y" type="int"/>
+      <arg name="width" type="int"/>
+      <arg name="height" type="int"/>
+    </request>
+
+    <!-- Version 3 additions -->
+
+    <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.
+
+	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="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
@@ -391,13 +456,14 @@
       </description>
     </request>
 
-    <request name="unset_moving" since="2">
+    <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">