4 ms·
Everything is outsourced to the compositor. It's insane. Same reason there's no xbindkeys for Wayland - every compositor needs to implement their own version
by costco 2y ago
Everything is outsourced to the compositor. It's insane. Same reason there's no xbindkeys for Wayland - every compositor needs to implement their own version of it. Every compositor needs their own screen reader and accessibility software as well. All in the name of preventing mythical attack surface (people write exploits to give themselves arbitrary code execution, not for the ability to read window contents or whatever Wayland is supposed to prevent).
- t0astbread 2y agoIsn't screen reader support implemented using AT-SPI over D-Bus? So I would expect it to be independent of the window system. On https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/ https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/ it even says: > Wayland > Works just the same :D Apart from that while it's true that the compositor has to do everything, some of the interfaces seem to be shared (standardized? I don't know enough about Wayland development tbh) across different compositors: https://wayland.app/protocols/ https://wayland.app/protocols/
- rcxdude 2y agoThat part is not so much about security: it would be entirely possible to make a secure standard protocol for such things, it's just there's enough highly opinionated people involved that no-one can agree and they each do their own thing.