https://bugs.kde.org/show_bug.cgi?id=489983
--- Comment #8 from Zamundaaa <xaver.h...@gmail.com> --- > This is very much a problem if, say, a client resizes itself, and the > compositor sends a configure event with an old size due to a state change That problem does not go away unless the client always completely ignores configure events, which is not acceptable. > It's also saying that there is no way that a client can un-maximize and > immediately request a new floating size Yes, that is not really supported by the protocol right now, unless the compositor sends a configure event with size 0. If you'd like to have that supported, it would need changes in the protocol to bundle unset_maximized with a desired size hint. In practice it's never been an issue though. -- You are receiving this mail because: You are watching all bug changes.
