Commit 36cee4bd authored by Simon Ser's avatar Simon Ser
Browse files

xdg-activation-v1: clarify set_{serial,surface}



Make it clearer what the requests are used for.
Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
parent 353ffc65
Pipeline #351671 passed with stages
in 46 seconds
......@@ -120,6 +120,14 @@
Provides information about the seat and serial event that requested the
token.
The serial can come from an input or focus event. For instance, if a
click triggers the launch of a third-party client, the launcher client
should send a set_serial request with the serial and seat from the
wl_pointer.button event.
Some compositors might refuse to activate toplevels when the token
doesn't have a valid and recent enough event serial.
Must be sent before commit. This information is optional.
</description>
<arg name="serial" type="uint"
......@@ -140,11 +148,14 @@
</request>
<request name="set_surface">
<description summary="specifies the application being activated">
The requesting client can specify a surface to associate the token
being created with it.
<description summary="specifies the surface requesting activation">
This request sets the surface requesting the activation. Note, this is
different from the surface that will be activated.
Some compositors might refuse to activate toplevels when the token
doesn't have a requesting surface.
Must be triggered before commit. This information is optional.
Must be sent before commit. This information is optional.
</description>
<arg name="surface" type="object" interface="wl_surface"
summary="the requesting surface"/>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment