4 ms·
It breaks everything of the sort. On X11, a client can view the contents of any arbitrary window, simulate input, read input — this is necessary obviously for
by Blikkentrekker 6y ago
It breaks everything of the sort.
On X11, a client can view the contents of any arbitrary window, simulate input, read input — this is necessary obviously for screen sharing applications; though one can argue that maybe a permission model needs to exist to allow some clients to run with lower privileges — the funny thing is that it does; it's called te XSECURITY extension, it's very easy to use, and seldom used for whatever reason though SSH uses it whenever it can.
On Wayland, no client can do such things, but many clients such as screen sharing tools, profiling tools, and whatever else that needs to simulate input and read surfaces obviously needs to.
Wayland developers simply say “It must be built into the compositor”, but no compositor can be expected to provide all that, and no compositor does.
- cycloptic 6y agoThe reason XSECURITY is not used is because it's not a real client API and it breaks applications. All it can do is force certain protocol requests to error out or return garbage data. In wayland the security method has moved towards asynchronously showing a dialog asking for permission. It's not feasible to modify the X11 protocol to have it do that without causing more breakage in applications. >no compositor does This is not correct. GNOME's compositor actually does support screen sharing, sharing of individual surfaces, and simulated input. And I'm not entirely sure what you mean by profiling tools, can you elaborate?