Implemented & Planned Wayland protocols

[PolyMeilex]

• ✔️ - Done
• 🔻 - Low priority / obscure / superseded / mostly unused in the ecosystem
• 🚧 - WIP

Core

Protocol		Implemented / Latest Version
wl_compositor	✔️	6
wl_subcompositor	✔️	1
wl_shm	✔️	1 / 2
wl_data_device_manager	✔️	3
wl_seat	✔️	9
wl_output	✔️	4

Stable

Protocol		Implemented / Latest Version
wp_presentation	✔️	1
wp_viewporter	✔️	1
xdg_shell	✔️	6
linux-dmabuf-v1	✔️	5
wp_tablet-v2	🚧	1 (partial)

Staging

Protocol		Implemented / Latest Version
xdg_activation-v1	✔️	1
wp_alpha_modifier-v1	🚧 (#1426)
wp_drm_lease-v1	✔️	1
wp_linux_drm_syncobj-v1	🚧 (#1356)
ext_session_lock-v1	✔️
wp_single_pixel_buffer-v1	🚧 (#988, #719)
wp_content_type-v1	✔️	1
ext_idle_notify-v1	✔️	1
wp_tearing_control-v1	🚧 (#1325)
xwayland_shell-v1	✔️	1
wp_fractional_scale-v1	✔️	1
cursor-shape-v1	✔️	1
ext-foreign-toplevel-list-v1
security-context-v1	✔️	1
ext-transient-seat-v1
xdg-toplevel-drag-v1
xdg-dialog-windows-v1	🚧 (#1389)

Unstable

Protocol		Implemented / Latest Version
wp_fullscreen_shell-v1	🔻	Not used by any mainstream compositor
wp_idle_inhibit-v1	✔️	1
wp_input_method-v2	✔️	1
wp_input_timestamps-v1	🔻	After 6y still used only by Weston
wp_keyboard_shortcuts_inhibit-v1	✔️	1
wp_explicit_synchronization-v1	🔻	Superseded by linux-drm-syncobj
wp_pointer_constraints-v1	✔️	1
wp_pointer_gestures-v1	✔️	3
wp_primary_selection-v1	✔️	1
wp_relative_pointer-v1	✔️	1
wp_text_input-v3	✔️	1
xdg_decoration-v1	✔️	1
xdg_foreign-v2	✔️	1
xdg_output-v1	✔️	3
xwayland_keyboard_grab-v1	✔️	1

Unstandardised

Protocol		Implemented / Latest Version
wlr-layer-shell-v1	✔️	4 / 5
KDE server-decoration	✔️	1
virtual-keyboard-v1	✔️	1
wlr-data-control-v1	✔️	2

---

Feel free to edit this as needed.

[orowith2os]

Should the KDE SSD and virtual-keyboard-v1 protocols be supported still? We have xdg-decoration and the v2 of the virtual keyboard protocols already.

If clients don't support them, it would probably be better to fix the clients than work around their issues.

[Drakulix]

Especially kde-decoration is incredibly small and not really a maintenance burden, but (funnily enough) GTK of all toolkits has not yet moved to xdg-decoration.

There is an open PR to fix that, but that one hasn't received attention in years...

[orowith2os]

For readers: I've made a PR upstream to fix the issue, and in the process, caused the world to burn:

https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6161

[DemiMarie]

Is wp_explicit_synchronization-v1 really obscure? The only user is likely to be Mesa but Mesa is used by just about everything.

[orowith2os]

@DemiMarie the ecosystem is still implicitly synced right now, so the v1 protocol is mostly irrelevant - time would be better put towards the v2 protocol and migrating to that.

[DemiMarie]

@orowith2os ah, okay

[PolyMeilex]

My reasoning when assigning the low priority icons was "are there any compositors that use this protocol", and information on that was gathered by my wlprobe tool (basically wayland-info but outputs JSON).

Output of those probes is being published in compositor support section of wayland.app eg. https://wayland.app/protocols/linux-explicit-synchronization-unstable-v1#compositor-support

So unless the global is not visible to regular clients (like xwayland_keyboard_grab-v1) this basically means that no mainstream compositor advertises this global. If that's not the case, I might need to remove that badge.

[megatux]

Is wlr input inhibitor planned? I tried today swaylock-effects and requires it (on Niri).

[Drakulix]

Is wlr input inhibitor planned? I tried today swaylock-effects and requires it (on Niri).

No. The main use case of this protocol has been replaced by ext-session-lock. swaylock-effects should be updated to use the new protocol (as does upstream swaylock).

[megatux]

Oh, cool, thanks. Seems there are commits on that project to use the newer protocol. Probably not released yet. Regards