wayland-protocols.git/staging/xdg-activation, branch masteraction binder protocol
https://git.vlhl.dev/navi/wayland/wayland-protocols.git/atom?h=master2022-12-19T12:41:52+00:00Fix typo in xdg-activation-v12022-12-19T12:41:52+00:00Philip Withnallphilip@tecnocode.co.uk2022-12-19T12:37:57+00:00urn:sha1:37a7b9d387f01ae789432872028317488d0000c8
Noticed during review in
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/98#note_1003427,
but not changed at the time.
Noticed again in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3090#note_1606895.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
xdg-activation: rewrite and move description of token forwarding2021-08-04T15:20:35+00:00Roman Gilgsubdiff@gmail.com2021-06-15T12:50:17+00:00urn:sha1:7460f79e4b10bcba20f32af28286955ecf0b9105
After a requesting client receives a new token, the client usually forwards the
token string to another client by a different process, which then uses the
token in an activate request. For that the token string must be transferred to
the other process.
Two default ways of doing that were described in the done event, but the
description had some issues and it makes more sense to describe them in the
protocol description itself, which talks about the protocol in a more general
way. Therefore rewrite the paragraphs about token forwarding between clients
and place them in the protocol description.
Signed-off-by: Roman Gilg <subdiff@gmail.com>
xdg-activation: correct sequence when X11 client spawns Wayland client2021-08-04T15:20:35+00:00Roman Gilgsubdiff@gmail.com2021-06-15T11:17:21+00:00urn:sha1:855786de9195c2b5ad2780e1b4869e0de0ef9f39
The Wayland client requests surface activation directly using the token
that it received from the X11 client.
Signed-off-by: Roman Gilg <subdiff@gmail.com>
xdg-activation: use rst inline code2021-08-04T15:20:35+00:00Roman Gilgsubdiff@gmail.com2021-06-15T11:10:06+00:00urn:sha1:e7183fb762bc4b1724aef563c53286756357846c
rst requires two backticks to format text as inline code.
Signed-off-by: Roman Gilg <subdiff@gmail.com>
xdg-activation: use rst link2021-08-04T15:20:35+00:00Roman Gilgsubdiff@gmail.com2021-06-15T11:04:26+00:00urn:sha1:7391c8e42f5c55b2e5a9f790f768cf2785f77de4
Instead of writing the link in brackets use the rst link functionality.
Signed-off-by: Roman Gilg <subdiff@gmail.com>
xdg-activation-v1: clarify set_{serial,surface}2021-07-01T20:38:30+00:00Simon Sercontact@emersion.fr2021-06-02T18:42:27+00:00urn:sha1:36cee4bdbcaf3a75f567315809953b5e21d703da
Make it clearer what the requests are used for.
Signed-off-by: Simon Ser <contact@emersion.fr>
xdg-activation: Fix an inconsistency2021-06-07T16:50:13+00:00Vlad Zahorodniivlad.zahorodnii@kde.org2021-05-27T11:31:25+00:00urn:sha1:577bdce99de972e14722cb05f92f6d99eb7f584a
The spec uses the terms "presentation token" and "activation token"
interchangeably, which can cause confusion.
Signed-off-by: Vlad Zahorodnii <vlad.zahorodnii@kde.org>
staging/xdg-activation: Describe interoperation with X112021-04-30T12:26:54+00:00Carlos Garnachocarlosg@gnome.org2020-12-03T15:59:54+00:00urn:sha1:2939d4a05ef2f66101ac8071f365dd8b07ed0f42
X11 had its own startup notification protocol, describe how could Wayland
compositors implement interoperation between Wayland and X11 clients,
should this be desired.
Signed-off-by: Carlos Garnacho <carlosg@gnome.org>
Include a new xdg_activation protocol2021-04-30T12:26:50+00:00Aleix Polaleixpol@kde.org2020-10-15T13:49:41+00:00urn:sha1:032a0bdc9b293bfa04a691f92a85ab88d4907447
Signed-off-by: Aleix Pol Gonzalez <aleixpol@kde.org>
Reviewed-by: David Edmundson <davidedmundson@kde.org>
Reviewed-by: Simon Ser <contact@emersion.fr>
Reviewed-by: Jonas Ådahl <jadahl@gmail.com>