Add set_autohide_systemui to wayland 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 168 matching lines @@
       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.
 
       For a surface to be mapped by the compositor the client must have
       committed both an remote_surface state and a buffer.
     </description>
 
+    <enum name="systemui_autohide_state">

[oshima, 2017/03/28 23:54:47]

it's probably better to call this systemui_visibility_state

[yorkelee, 2017/03/29 00:15:09]

Done.

+      <description summary="systemui autohide behavior">
+         Determine the autohide behavior of the system UI.
+      </description>
+      <entry name="visible" value="1" summary="system ui is visible"/>
+      <entry name="autohide_non_sticky" value="2" summary="system ui autohides and is not sticky"/>
+      <entry name="autohide_sticky" value="3" summary="system ui autohides and is sticky"/>
+    </enum>
+
     <request name="destroy" type="destructor">
       <description summary="Destroy the remote_surface">
         Unmap and destroy the window. The window will be effectively
         hidden from the user's point of view, and all state will be lost.
       </description>
     </request>
 
     <request name="set_app_id">
       <description summary="set application ID">
         Set an application identifier for the surface.
@@ skipping 224 matching lines @@
         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 -->
+    <request name="set_autohide_systemui" since="3">

[oshima, 2017/03/28 23:54:47]

set_systemui_visibility

[yorkelee, 2017/03/29 00:15:09]

Done.

+      <description summary="requests the system ui autohide behavior for the surface">
+        Requests how the surface will autohide the system UI when it is made active.
+      </description>
+      <arg name="autohide" type="uint"/>
+    </request>
 
-    <event name="configure" since="3">
+    <!-- Version 4 additions -->
+
+    <event name="configure" since="4">
       <description summary="suggest a surface change">
         The configure event asks the client to change surface state.
 
         The client must apply the origin offset to window positions in
         set_window_geometry requests.
 
         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_offset_x" type="int"/>
       <arg name="origin_offset_y" type="int"/>
       <arg name="states" type="array"/>
       <arg name="serial" type="uint"/>
     </event>
 
-    <request name="ack_configure" since="3">
+    <request name="ack_configure" since="4">
       <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="move" since="3">
+    <request name="move" since="4">
       <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
@@ skipping 10 matching lines @@
     </description>
 
     <request name="destroy" type="destructor">
       <description summary="Destroy the notification_surface">
         Unmap and destroy the notification surface.
       </description>
     </request>
   </interface>
 
 </protocol>