third_party: Update to version 6 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 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="5">
+  <interface name="zwp_remote_shell_v1" version="6">
     <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.
       </description>
       <entry name="default" value="1" summary="default container"/>
       <entry name="overlay" value="2" summary="system modal container"/>
     </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>
 
     <request name="destroy" type="destructor">
       <description summary="destroy remote_shell">
         Destroy this remote_shell object.
 
         Destroying a bound remote_shell object while there are surfaces
         still alive created by this remote_shell object instance is illegal
         and will result in a protocol error.
       </description>
     </request>
 
     <request name="get_remote_surface">
       <description summary="create a remote shell surface from a surface">
         This creates an remote_surface for the given surface and gives it the
         remote_surface role. A wl_surface can only be given a remote_surface
         role once. If get_remote_surface is called with a wl_surface that
         already has an active remote_surface associated with it, or if it had
         any other role, an error is raised.
 
         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>
 
+    <request name="get_notification_surface" since="6">

[reveman, 2016/06/23 18:28:00]

please move this down to "Version 6 additions" section

[xiyuan, 2016/06/23 18:34:11]

Added a "Version 6 additions" section for zwp_remote_shell_v1 interface and move
it there.

+      <description summary="create a notification surface from a surface">
+        Creates a notification_surface for the given surface, gives it the
+        notification_surface role and associated it with a notification id.
+      </description>
+      <arg name="id" type="new_id" interface="zwp_notification_surface_v1"/>
+      <arg name="surface" type="object" interface="wl_surface"/>
+      <arg name="notification_id" type="string" />
+    </request>
+
     <event name="configure">
       <description summary="suggests a re-layout of remote shell">
         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">
       <description summary="activated surface changed">
         Notifies client that the activated surface changed.
       </description>
       <arg name="gained_active" type="object" interface="wl_surface" allow-null="true"/>
       <arg name="lost_active" type="object" interface="wl_surface" allow-null="true"/>
     </event>
   </interface>
 
-  <interface name="zwp_remote_surface_v1" version="5">
+  <interface name="zwp_remote_surface_v1" version="6">
     <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 271 matching lines @@
     <request name="set_top_inset" since="5">
       <description summary="set top inset for surface">
         Set distance from the top of the surface to the contents.
 
         This distance typically represents the size of the window caption.
       </description>
       <arg name="height" type="int"/>
     </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>