It doesn't, it just delegates the responsibility to something else, namely xdg-desktop-portal and/or your compositor. The main issue with global hotkeys is that applications can't usually set them, e.g. Discord push-to-talk, rather the compositor has to set them and the application needs to communicate with the compositor. This is fundamentally different from how it worked with X11 so naturally adoption is slow.

[–] AVincentInSpace@pawb.social 4 points 4 months ago (1 children)

Well yeah. Wayland is a protocol, not an application. There's nothing it can do except delegate to one of the two ends of the connection.

[–] kogasa@programming.dev 2 points 4 months ago (1 children)

These things are specifically not defined by the protocol. They could be. They're not, by design.

[–] AVincentInSpace@pawb.social 2 points 4 months ago* (last edited 4 months ago) (1 children)

I agree that the deliberate design simplicity of vanilla Wayland is to its detriment, as does anyone who has ever interacted with Wayland. That said, there are extensions to the protocol which have been ratified by XDG and are supported by most compositors and applications that remedy most of those issues.

[–] renzev@lemmy.world 1 points 4 months ago

Isn't that also more or less the case with X11? From what I understand, if you try to use bare Xorg without any extensions like Xfixes and Xdamage, it's pretty miserable