Skip to content

xdg-shell: clarify unmapping behavior with configures

Unmapping an xdg_toplevel means ... The xdg_toplevel returns to the state it had right after xdg_surface.get_toplevel.

Does this apply to sent configures?

Consider the following behavior: (wl_surface@3 is originally mapped)

[3582037.486] xdg_surface@7.configure(64882)
[3582037.587]  -> wl_surface@3.attach(nil, 0, 0)
[3582037.657]  -> wl_surface@3.commit()
[3582037.726]  -> xdg_surface@7.ack_configure(64882)

Based on the description one could assume that this would be invalid, however, KWin, Mutter, and Weston seem to allow it.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information