Add new wayland request to enter screen locking mode.

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="10">
+  <interface name="zwp_remote_shell_v1" version="11">
     <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="state_type">
       <description summary="state types for remote surfaces">
         Defines common show states for shell surfaces.
       </description>
       <entry name="normal" value="1" summary="normal window state"/>
       <entry name="minimized" value="2" summary="minimized window state"/>
       <entry name="maximized" value="3" summary="maximized window state"/>
       <entry name="fullscreen" value="4" summary="fullscreen window state"/>
       <entry name="pinned" value="5" summary="pinned window state"/>
+      <entry name="trusted_pinned" value="6" summary="trusted pinned window state"/>
     </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>
 
     <enum name="layout_mode">
       <description summary="the layout mode">
@@ skipping 84 matching lines @@
       <arg name="transform" type="int"/>
       <arg name="scale_factor" type="fixed"/>
       <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="10">

[hidehiko, 2016/08/24 16:13:12]

Could you update this to 11, too?

[hirono, 2016/08/25 03:30:12]

Done.

     <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 316 matching lines @@
     </request>
 
     <!-- Version 10 additions -->
 
     <request name="activate" since="10">
       <description summary="make the surface active">
         Make the surface active and bring it to the front.
       </description>
       <arg name="serial" type="uint" summary="the serial of the user event"/>
     </request>
+
+    <!-- Version 11 additions -->
+    <request name="pin" since="11">

[reveman, 2016/08/24 18:47:47]

there's already a request with this name as part of the interface. even if this
happens to work, please use a different name to avoid confusion. pin_trusted?

[hirono, 2016/08/25 03:30:12]

Yes, I was confused with the name in <description summary="">. Done

+      <description summary="pinWithTrustedFlag">

[hidehiko, 2016/08/24 16:13:12]

Could you use snake_case_name ?

[reveman, 2016/08/24 18:47:47]

this should be a short sentence that describes the request

[hirono, 2016/08/25 03:30:12]

Done.

[hirono, 2016/08/25 03:30:12]

Done.

[hidehiko, 2016/08/25 06:19:40]

Oops, I was also confused. Sorry for mis-leading, hirono-san, and thank you for
pointing this out, David.

+        Request that surface is pinned.
+
+        This is only a request that the window should be pinned.
+        The compositor may choose to ignore this request. The client should
+        listen to set_pinned events to determine if the window was
+        pinned or not. If trusted flag is non-zero, the app can prevent users
+        from exiting the pinned mode.
+      </description>
+      <arg name="trusted" type="int" summary="whether the app can enforce usres

[hidehiko, 2016/08/24 16:13:12]

s/usres/users/

+          to stay in the pinned mode."/>
+    </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>