<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - gtk_window_move() unreliable in Wayland?" href="https://bugzilla.gnome.org/show_bug.cgi?id=757558#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - gtk_window_move() unreliable in Wayland?" href="https://bugzilla.gnome.org/show_bug.cgi?id=757558">bug 757558</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>I think we maybe should complain more verbosely in the Wayland GDK when things won't work properly. For example, if a toplevel window is moved, we should complain saying moving doesn't work for toplevel windows. We have started to complain some when a window that should be mapped as a popup is not actually mapped as a popup, but we can also start complaining when the application tries to move an already mapped popup. We should also consider how to deal with things that should be mapped as subsurfaces, since we currently are a bit lax on the order of transiency and showing (we ad-hoc map when transiency is set for those), and that makes it hard to warn when things go wrong. I don't see how we can make it work reliably without going all GTK+ 4 though. Can we add more detailed semantics of the different window types right now and then just force applications to play with those rules in order to work?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>