forked from AuroraMiddleware/gtk
7f12dc2b66
An application may want to set a fallback size of a window while still mapping maximized. This is done by calling gtk_window_resize() before gtk_window_maximize() and before gtk_window_show(). When the window is mapped, it should have a maximized size, and if it eventually is unmaximized, it should fall back to the size from the earlier gtk_window_resize() call. What happens before this commit is that the initial window size ends up respecting the first gtk_window_resize() dimensions, and not the window dimension configured by the Wayland display server (i.e. maximized dimensions). Fix this by postponing any configure events until we received our configuration from the display server. If we got one with a fixed size (e.g. we're maximized, tiled etc), we use that, otherwise we look at the one that was previously configured by gtk which corresponds to the "preferred" size when not being maximized. This fixes Firefox being started in a maximized state when using the Wayland backend. Closes: https://gitlab.gnome.org/GNOME/gtk/-/issues/2538 |
||
|---|---|---|
| .. | ||
| protocol | ||
| gdkapplaunchcontext-wayland.c | ||
| gdkcursor-wayland.c | ||
| gdkdevice-wayland.c | ||
| gdkdisplay-wayland.c | ||
| gdkdisplay-wayland.h | ||
| gdkdnd-wayland.c | ||
| gdkeventsource.c | ||
| gdkglcontext-wayland.c | ||
| gdkglcontext-wayland.h | ||
| gdkkeys-wayland.c | ||
| gdkmonitor-wayland.c | ||
| gdkmonitor-wayland.h | ||
| gdkprivate-wayland.h | ||
| gdkscreen-wayland.c | ||
| gdkseat-wayland.h | ||
| gdkselection-wayland.c | ||
| gdkwayland.h | ||
| gdkwaylanddevice.h | ||
| gdkwaylanddisplay.h | ||
| gdkwaylandglcontext.h | ||
| gdkwaylandmonitor.h | ||
| gdkwaylandselection.h | ||
| gdkwaylandwindow.h | ||
| gdkwindow-wayland.c | ||
| Makefile.am | ||
| meson.build | ||
| wm-button-layout-translation.c | ||
| wm-button-layout-translation.h | ||