https://bugzilla.gnome.org/show_bug.cgi?id=710652 gtk+ | wayland | 3.10.x
--- Comment #2 from Philip Withnall <[email protected]> 2013-11-05 12:48:47 UTC --- This fixes the immediate problem, but further work is needed on the documentation for the GTK+ and GDK fullscreening and maximisation APIs. The current behaviour on the Wayland backend is that (e.g.) calling: 1. gtk_window_fullscreen() 2. gtk_window_maximize() 3. gtk_window_unmaximize() will result in a normal window, not a fullscreened window. In other words, the states don’t stack. This is potentially in conflict with the X11 backend (I haven’t tested), and certainly isn’t mentioned in the documentation. Either the documentation needs amending to state that this is the expected behavior (which would be reasonable, I think); or the Wayland backend needs some minor refactoring so that fullscreen/maximisation/transient states are stackable. See http://wayland.freedesktop.org/docs/html/protocol-spec-interface-wl_shell_surface.html, and especially wl_shell_surface::set_toplevel, for information about how Wayland treats fullscreen, maximised and transient windows. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
