https://bugs.freedesktop.org/show_bug.cgi?id=107358
--- Comment #13 from Olivier Fourdan <four...@xfce.org> ---
(In reply to mikhail.v.gavrilov from comment #12)
> (In reply to Olivier Fourdan from comment #10)
> > It is normal because this is how X11 is designed, this is part of the
> > protocol, applications can issue an active grab on input devices and block
> > other clients from receiving input events:
>
> And you don't plan redesign X11 clients behaviour under Wayland environment?
No, because the purpose of Xwayland is precisely to allow legacy X11 clients to
run unchanged on a Wayland compositor.
In theory, it would be possible to change Xwayland to pretend a grab succeeded
but not actually issue the active grabs even when the clients request it, but
that will break those X11 clients that rely on grabs to work.
Besides, not all clients can be ported/redesigned. There are old, legacy,
closed source, in-house software that nobody knows how to recompile that run on
X11 for years and will never be ported to Wayland, this is where Xwayland comes
into play. For those, we want Xwayland to behave like any other X11 server.
If developers on such X11 clients had to redesign X11 clients for Wayland,
they'd rather spend their time porting to Wayland native instead, I reckon.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
