arc: Implement proper Arc window activation for task moving to front.

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="8">
+  <interface name="zwp_remote_shell_v1" version="9">
     <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.
@@ skipping 91 matching lines @@
       <description summary="layout mode changed">
         The shell_mode_changed event is sent by the compositor when
         the shell mode was changed.
 
         This is an event to notify that the shell mode has switched.
       </description>
       <arg name="layout_mode" type="uint"/>
     </event>
   </interface>
 
-  <interface name="zwp_remote_surface_v1" version="8">
+  <interface name="zwp_remote_surface_v1" version="9">
     <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 298 matching lines @@
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become system modal.
       </description>
     </request>
 
     <request name="unset_system_modal" since="8">
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become non system modal.
       </description>
     </request>
+
+    <!-- Version 9 additions -->
+
+    <request name="activate" since="9">

[reveman, 2016/08/01 00:52:41]

Oh, one thing. Can you add:

<arg name="serial" type="uint" summary="the serial of the user event"/>

the client side code can just past the serial of the last input event or 0. and
the exo code can just ignore it for now but it allows us to implement focus
stealing prevention in the near future without having to update the interface.

[khmel, 2016/08/02 02:21:53]

Thanks David for offline chat, done

+      <description summary="make the surface active">
+        Make the surface active and bring it to the front.
+      </description>
+    </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>