Add configuration_changed event and set_background_opacity request.

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="zwp_remote_shell_v1" version="8">
+  <interface name="zwp_remote_shell_v1" version="9">
     <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 48 matching lines @@
         See the documentation of remote_surface for more details about what an
         remote_surface is and how it is used.
       </description>
       <arg name="id" type="new_id" interface="zwp_remote_surface_v1"/>
       <arg name="surface" type="object" interface="wl_surface"/>
       <arg name="container" type="uint"/>
     </request>
 
     <event name="configure">
       <description summary="suggests a re-layout of remote shell">
-        Suggests a re-layout of remote surface geometry.
+        Obsolete: Suggests a re-layout of remote surface geometry.
       </description>
       <arg name="width" type="int"/>
       <arg name="height" type="int"/>
       <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"/>
     </event>
 
     <event name="activated">
@@ skipping 20 matching lines @@
 
     <event name="layout_mode_changed" since="8">
       <description summary="layout mode changed">
         The shell_mode_changed event is sent by the compositor when
         the shell mode was changed.
 
         This is an event to notify that the shell mode has switched.
       </description>
       <arg name="layout_mode" type="uint"/>
     </event>
+
+    <!-- Version 9 additions -->
+
+    <event name="configuration_changed" since="9">
+      <description summary="suggests a re-configuration of remote shell">
+        Suggests a re-configuration of remote shell.
+      </description>
+      <arg name="width_physical_pixels" type="int"/>
+      <arg name="height_physical_pixels" type="int"/>
+      <arg name="dpi" type="fixed"/>
+      <arg name="transform" type="int"/>
+      <arg name="refresh_rate_mhz" type="int"/>
+      <arg name="scale_factor" type="fixed"/>
+      <arg name="width" type="int"/>
+      <arg name="height" type="int"/>

[reveman, 2016/07/29 16:03:51]

I took a good look at our client code and the only arguments out of the above
that we really need are the following:

<arg name="width" type="int"/>
<arg name="height" type="int"/>
<arg name="transform" type="int"/>
<arg name="scale_factor" type="fixed"/>

as refresh rate is not really used as we now provide proper vsync events so it's
fine to hard code 60hz in hwc code. dpi and physical size can't change on the
client side so it's much better to just compute those values there based on the
density property.

Ping me if this doesn't match what you see in the client code.

[oshima, 2016/07/29 19:27:03]

Are you suggesting to just give them fake value? There is no way to get the
correct value
even for the first detected one without them.

+      <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="zwp_remote_surface_v1" version="8">
+  <interface name="zwp_remote_surface_v1" version="9">
     <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 298 matching lines @@
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become system modal.
       </description>
     </request>
 
     <request name="unset_system_modal" since="8">
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become non system modal.
       </description>
     </request>
+
+    <!-- Version 9 additions -->
+
+    <request name="set_rectangular_shadow_background_opacity" since="9">
+      <description summary="suggests the window's background opacity">
+        Suggests the window's background opacity when the shadow is requested.
+      </description>
+      <arg name="opacity" type="fixed"/>
+    </request>
+
   </interface>
 
   <!-- Version 6 additions -->
 
   <interface name="zwp_notification_surface_v1" version="6">
     <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>