Use pixel coordinates for shadow underlay bounds

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 20 matching lines @@
     Warning! The protocol described in this file is experimental and backward
     incompatible changes may be made. Backward compatible changes may be added
     together with the corresponding interface version bump. Backward
     incompatible changes are done by bumping the version number in the protocol
     and interface names and resetting the interface version. Once the protocol
     is to be declared stable, the 'z' prefix and the version number in the
     protocol and interface names are removed and the interface version number is
     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
       and made fullscreen by the user.
     </description>
 
     <enum name="container">
       <description summary="containers for remote surfaces">
         Determine how a remote surface should be stacked relative to other
         shell surfaces.
@@ skipping 81 matching lines @@
       <arg name="transform" type="int"/>
       <arg name="scale_factor" type="fixed"/>
       <arg name="work_area_inset_left" type="int"/>
       <arg name="work_area_inset_top" type="int"/>
       <arg name="work_area_inset_right" type="int"/>
       <arg name="work_area_inset_bottom" type="int"/>
       <arg name="layout_mode" type="uint"/>
     </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
       and allows for remotely managed windows.
 
       It provides requests to treat surfaces like windows, allowing to set
       properties like app id and geometry.
 
       The client must call wl_surface.commit on the corresponding wl_surface
       for the remote_surface state to take effect.
@@ skipping 46 matching lines @@
 
     <request name="set_scale">
       <description summary="set scale">
         Set a scale factor that will be applied to surface and all descendants.
       </description>
       <arg name="scale" type="fixed"/>
     </request>
 
     <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.
 
         The arguments are given in the output coordinate space and specifies
         the inner bounds of the shadow.
 
         The arguments are given in the output coordinate space.
         Specifying zero width and height will disable the shadow.
       </description>
@@ skipping 154 matching lines @@
         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 -->
 
-    <event name="configure" 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="2">
+    <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="2">
+    <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.
       </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">
     <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>