Why would a program EVER need to do this? It’s a feature that for every program that has a valid use for it, there are 99 programs that use it in some malicious way.
I’m gonna need you to convince me that there exist 99 programs that use it maliciously.
Meanwhile I just had to add support for doing this to Unreal because it’s the only way to change displays from in-game menus. Also I remember a number of browser demos/games that created/managed multiple windows with objects that would fly between them. I’ve never seen it used maliciously.
TIL that Wayland doesn’t support a program positioning it’s window with absolute coordinates on purpose.
Thats… uh. That’s kinda broken.
Why would a program EVER need to do this? It’s a feature that for every program that has a valid use for it, there are 99 programs that use it in some malicious way.
There are some use cases here: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247
Almost all of these should change how they behave instead of carrying on design that was acceptable maybe 15 years ago.
But this problem has already been fixed with xdg_wm_base::create_positioner
I’m gonna need you to convince me that there exist 99 programs that use it maliciously.
Meanwhile I just had to add support for doing this to Unreal because it’s the only way to change displays from in-game menus. Also I remember a number of browser demos/games that created/managed multiple windows with objects that would fly between them. I’ve never seen it used maliciously.
AFAIK that’s also a big hurdle for wine, but they had figured out how to make everything work eventually.