From 855786de9195c2b5ad2780e1b4869e0de0ef9f39 Mon Sep 17 00:00:00 2001 From: Roman Gilg Date: Tue, 15 Jun 2021 13:17:21 +0200 Subject: 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: Roman Gilg --- staging/xdg-activation/x11-interoperation.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/staging/xdg-activation/x11-interoperation.rst b/staging/xdg-activation/x11-interoperation.rst index 83196e9..3bd03ee 100644 --- a/staging/xdg-activation/x11-interoperation.rst +++ b/staging/xdg-activation/x11-interoperation.rst @@ -43,12 +43,11 @@ Scenario 2. X11 client spawns Wayland client 4. X11 client spawns Wayland client, sets ``$DESKTOP_STARTUP_ID`` in its environment. 5. Wayland client starts. -6. Wayland client sets the activation token, as received from - ``$DESKTOP_STARTUP_ID``. +6. Wayland client requests surface activation with the activation token, + as received from ``$DESKTOP_STARTUP_ID``. 7. Compositor receives the request, matches ID with the common pool 8. The startup feedback is finished. -9. Wayland client requests surface activation. -10. Compositor applies internal policies to allow/deny focus switch. +9. Compositor applies internal policies to allow/deny focus switch. Caveats ------- -- cgit v1.2.3