ext-foreign-toplevel-list-v1: increase identifier size to 48

Signed-off-by: Julian Orth <ju.orth@gmail.com>
This commit is contained in:
Julian Orth 2026-04-27 13:30:26 +02:00
parent 911ab509ed
commit 7ee9b3b83a

View file

@ -51,7 +51,7 @@
only be done by creating a new major version of the extension.
</description>
<interface name="ext_foreign_toplevel_list_v1" version="1">
<interface name="ext_foreign_toplevel_list_v1" version="2">
<description summary="list toplevels">
A toplevel is defined as a surface with a role similar to xdg_toplevel.
XWayland surfaces may be treated like toplevels in this protocol.
@ -120,7 +120,7 @@
</request>
</interface>
<interface name="ext_foreign_toplevel_handle_v1" version="1">
<interface name="ext_foreign_toplevel_handle_v1" version="2">
<description summary="a mapped toplevel">
A ext_foreign_toplevel_handle_v1 object represents a mapped toplevel
window. A single app may have multiple mapped toplevels.
@ -207,11 +207,12 @@
must not be reused. An identifier must not be reused by the compositor to
ensure there are no races when sharing identifiers between processes.
An identifier is a string that contains up to 32 printable ASCII bytes.
An identifier must not be an empty string. It is recommended that a
compositor includes an opaque generation value in identifiers. How the
generation value is used when generating the identifier is implementation
dependent.
In version 1, an identifier is a string that contains up to 32 printable
ASCII bytes. In version 2 and later, an identifier is a string that contains
up to 48 printable ASCII bytes. An identifier must not be an empty
string. It is recommended that a compositor includes an opaque
generation value in identifiers. How the generation value is used when
generating the identifier is implementation dependent.
</description>
<arg name="identifier" type="string"/>
</event>