hakutaku/tdesktop
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

init
Some checks failed
Docker. / Ubuntu (push) Has been cancelled
Details
User-agent updater. / User-agent (push) Failing after 15s
Details
Lock Threads / lock (push) Failing after 10s
Details
Waiting for answer. / waiting-for-answer (push) Failing after 22s
Details
Needs user action. / needs-user-action (push) Failing after 8s
Details
Can't reproduce. / cant-reproduce (push) Failing after 8s
Details
Close stale issues and PRs / stale (push) Has been cancelled
Details

Browse Source
This commit is contained in:
allhaileris
2026-02-16 15:50:16 +03:00
commit afb81b8278
13816 changed files with 3689732 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
Telegram/ThirdParty/xdg-desktop-portal/doc/window-identifiers.rst vendored Normal file
View File

@@ -0,0 +1,19 @@
Window Identifiers
==================
Most portals interact with the user by showing dialogs. These dialogs should
generally be placed on top of the application window that triggered them. To
arrange this, the compositor needs to know about the application window. Many
portal requests expect a ``"parent_window"`` string argument for this reason.
Under X11, the ``"parent_window"`` argument should have the form ``x11:<XID>``,
where ``<XID>`` is the XID of the application window in hexadecimal notation.
For example, ``x11:1234``.
Under Wayland, it should have the form ``wayland:<HANDLE>``, where ``<HANDLE>``
is a surface handle obtained with the `xdg_foreign
<https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml>`_
protocol. For example, ``wayland:~12l9jdl.-a``.
For other windowing systems, or if you don't have a suitable handle, just pass
an empty string for ``"parent_window"``.