Skip to content
Snippets Groups Projects
Commit 855786de authored by Roman Gilg's avatar Roman Gilg
Browse files

xdg-activation: correct sequence when X11 client spawns Wayland client


The Wayland client requests surface activation directly using the token
that it received from the X11 client.

Signed-off-by: default avatarRoman Gilg <subdiff@gmail.com>
parent e7183fb7
No related branches found
No related tags found
1 merge request!98xdg-activation: improve specification text and documentation
...@@ -43,12 +43,11 @@ Scenario 2. X11 client spawns Wayland client ...@@ -43,12 +43,11 @@ Scenario 2. X11 client spawns Wayland client
4. X11 client spawns Wayland client, sets ``$DESKTOP_STARTUP_ID`` in its 4. X11 client spawns Wayland client, sets ``$DESKTOP_STARTUP_ID`` in its
environment. environment.
5. Wayland client starts. 5. Wayland client starts.
6. Wayland client sets the activation token, as received from 6. Wayland client requests surface activation with the activation token,
``$DESKTOP_STARTUP_ID``. as received from ``$DESKTOP_STARTUP_ID``.
7. Compositor receives the request, matches ID with the common pool 7. Compositor receives the request, matches ID with the common pool
8. The startup feedback is finished. 8. The startup feedback is finished.
9. Wayland client requests surface activation. 9. Compositor applies internal policies to allow/deny focus switch.
10. Compositor applies internal policies to allow/deny focus switch.
Caveats Caveats
------- -------
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment