Add set_autohide_systemui to wayland protocol

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 12d061f3300265e327ee1d4bb71bd94a82a0146c..db7f93a624a321d1b4383b93e50922670b346e96 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
@@ -186,6 +186,15 @@
       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
@@ -430,8 +439,16 @@
     </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>
+
+    <!-- Version 4 additions -->
 
-    <event name="configure" since="3">
+    <event name="configure" since="4">
       <description summary="suggest a surface change">
 	The configure event asks the client to change surface state.
 
@@ -454,7 +471,7 @@
       <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
@@ -479,7 +496,7 @@
       <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.