From 577bdce99de972e14722cb05f92f6d99eb7f584a Mon Sep 17 00:00:00 2001
From: Vlad Zahorodnii <vlad.zahorodnii@kde.org>
Date: Thu, 27 May 2021 14:31:25 +0300
Subject: [PATCH] xdg-activation: Fix an inconsistency
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/xdg-activation-v1.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/staging/xdg-activation/xdg-activation-v1.xml b/staging/xdg-activation/xdg-activation-v1.xml
index d87e6337..377d690b 100644
--- a/staging/xdg-activation/xdg-activation-v1.xml
+++ b/staging/xdg-activation/xdg-activation-v1.xml
@@ -89,7 +89,7 @@
token and might decide not to follow through with the activation if it's
considered unwanted.
- Compositors can ignore unknown presentation tokens when an invalid
+ Compositors can ignore unknown activation tokens when an invalid
token is passed.
</description>
<arg name="token" type="string" summary="the activation token of the initiating client"/>
@@ -170,7 +170,7 @@
Applications implementing the D-Bus interface org.freedesktop.Application
should get their token under XDG_ACTIVATION_TOKEN on their platform_data.
- Presentation tokens may be transferred across clients through means not
+ Activation tokens may be transferred across clients through means not
described in this protocol.
</description>
<arg name="token" type="string" summary="the exported activation token"/>
--
GitLab