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..491b11c6a329cfec9785962e24aaac4db1585562 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
@@ -430,8 +430,17 @@
     </request>
 
     <!-- Version 3 additions -->
+    <request name="set_autohide_systemui" since="3">

[reveman, 2017/03/28 16:17:03]

hm, adding a version 3 request and making current version 3 api version 4 will
break existing clients. if client is not using version 3 api yet then why not
just make this part of version 3? if version 3 is used then this new request
must be version 4.

[yorkelee, 2017/03/28 16:23:59]

The client is not using version 3 api yet, and we are not landing the Android
side changes that use the multidisplay apis (that are currently version 3) in
m58. 

I don't think there are any clients that are currently using version 3 right
now, Dominik, can you confirm? 

[Dominik Laskowski, 2017/03/28 18:07:31]

Right, we should bump multi-display to version 4 so it doesn't block this from
landing in M58.

+      <description summary="requests whether the surface should autohide the system ui">
+  Requests whether or not the surface will autohide the system UI when it is

[oshima, 2017/03/28 16:18:17]

nit: indent

[yorkelee, 2017/03/28 17:33:26]

Done.

+  made active.
+      </description>
+      <arg name="autohide" type="int"/>

[oshima, 2017/03/28 16:18:18]

optional: you may want to use enum to support sticky behavior.

[yorkelee, 2017/03/28 17:33:26]

Done.

+    </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 +463,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 +488,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.