Patch 1 and 2 look fine to me. While it look a bit like a change in
semantics, given the possibility of race conditions etc, clients could
never make any assumptions about any state in future configure events.
The third patch, however, is more problematic, as it is possible that
clients may have m
From: Markus Ongyerth
v2 was
https://lists.freedesktop.org/archives/wayland-devel/2018-June/038734.html
Changes from v2:
Moved the word wrapping change into the first commit, as pointed out by Simon.
Markus Ongyerth (3):
xdg-shell: move maximized state definition together
xdg-shell: Make s
