4 ms·
Because it also has to simulate keypresses as the result of gestures. I don't think the Wayland world has an official way for non-compositor programs to send ke
by pritambaral 10y ago
Because it also has to simulate keypresses as the result of gestures. I don't think the Wayland world has an official way for non-compositor programs to send keypresses to any surface the program itself owns, in the name of security.
Which is a shame, I do dearly like xdotool etc. There should be a way to satisfy both security and function, a way to whitelist or permit special apps.
- eikenberry 10y agoI bet they will fix that somehow with Wayland. Tools like xdotool are pretty popular and if they don't support it officially, someone will come up with a hack around it.
- Elv13 10y ago> a hack around it. Nice choice of words here. The whole reason why it isn't supported is to prevent being hacked in the first place. X11 has no security whatsoever. Every window can read/spy/mess with any other. I guess only window managers / compositors will have enough permission to do this level of automation.
- shmerl 10y agoI suppose if this will be routed through the compositor, then it can provide needed security control.
- digi_owl 10y agoIIRC, not quite. with X11, every program that shares a root window can see the keypresses etc. Typically a root windows is the same as a screen, but i don't think there is anything that claim this to be a set in stone rule. But as is typical of Linux GUI devs, they much rather hack on the new shiny than try to maintain the existing stuff. And the new shiny these days is to put everything on the GPU.