(In reply to Mike Hommey [:glandium] [OOO Dec 30-Jan 8] from comment #10) > Wait, if wayland doesn't allow positioning, how does Xwayland do it? It doesn't generally do it, but the fact that in case of Gnome/KDE the X11 window manager is the same thing as the Wayland compositor means that the it can do it. You could think about this as kinda "privileged" Xwayland for better compatibility. This is different on e.g. ChromeOS where the Wayland compositor does not have any X11 support and Xwayland is a normal, non-privileged client (and part of the container/wm that Linux apps ship in). Here Xwayland has the same limitations as any other Wayland client thus doesn't support positioning. I'd expect XDG desktops to move into that direction as well over time, potentially making Xwayland part of Flatpak/Snap runtimes. But that's likely still a few years out.
Bug 1870955 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Mike Hommey [:glandium] [OOO Dec 30-Jan 8] from comment #10) > Wait, if wayland doesn't allow positioning, how does Xwayland do it? It doesn't generally do it, but the fact that in case of Gnome/KDE the X11 window manager is the same thing as the Wayland compositor means that it can do it. You could think about this as "privileged" Xwayland for better compatibility. This is different on e.g. ChromeOS where the Wayland compositor does not have any X11 support and Xwayland is a normal, non-privileged client (and part of the container/wm that Linux apps ship in). Here Xwayland has the same limitations as any other Wayland client thus doesn't support positioning. I'd expect XDG desktops to move into that direction as well over time, potentially making Xwayland part of Flatpak/Snap runtimes. But that's likely still a few years out.
(In reply to Mike Hommey [:glandium] [OOO Dec 30-Jan 8] from comment #10) > Wait, if wayland doesn't allow positioning, how does Xwayland do it? It doesn't generally do it, but the fact that in case of Gnome/KDE the X11 window manager is the same thing as the Wayland compositor means that it can do it. You could think about this as "privileged" Xwayland for better compatibility. This is different on e.g. ChromeOS where the Wayland compositor does not have any X11 support and Xwayland is a normal, non-privileged client (and part of the container/wm that Linux apps ship in). Here Xwayland has the same limitations as any other Wayland client thus doesn't support positioning. I'd expect XDG desktops to move into that direction as well over time, moving Xwayland out of the "system" layer and potentially making it part of Flatpak/Snap runtimes. But that's likely still a few years out.
(In reply to Mike Hommey [:glandium] [OOO Dec 30-Jan 8] from comment #10) > Wait, if wayland doesn't allow positioning, how does Xwayland do it? It doesn't generally do it, but the fact that in case of Gnome/KDE the X11 window manager is the same thing as the Wayland compositor means that it can do it. You could think about this as "privileged" Xwayland for better compatibility. This is different on e.g. ChromeOS where the Wayland compositor does not have any X11 support and Xwayland is a normal, non-privileged client (and part of the container/wm that Linux apps ship in). Here Xwayland has the same limitations as any other Wayland client and thus doesn't support positioning. I'd expect XDG desktops to move into that direction as well over time, moving Xwayland out of the "system" layer and potentially making it part of Flatpak/Snap runtimes. But that's likely still a few years out.