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 ed7226331846994f51b7ca285c98c08f597d28e9..2a721c73d02f77f6de58d88fe321188d06da40d9 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 |
@@ -38,7 +38,7 @@ |
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 |
@@ -63,6 +63,7 @@ |
<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"> |
@@ -504,6 +505,21 @@ |
</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 o
hirono
2016/08/25 03:30:12
Yes, I was confused with the name in <description
|
+ <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
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,
|
+ 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 --> |