https://bugs.kde.org/show_bug.cgi?id=252314
Tristan Miller <psychon...@nothingisreal.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|UPSTREAM |---
Status|RESOLVED |REOPENED
--- Comment #50 from Tristan Miller <psychon...@nothingisreal.com> ---
I reopened the report on the Emacs bug tracker at
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11113>. The developers there
have examined this KDE bug report and consulted the Window Manager
Specification at <https://www.freedesktop.org/wiki/Specifications/wm-spec/>,
and in their determination, this is definitely a problem with KWin and not
Emacs. In their view, the problem is due to KWin's failure to properly observe
geometry hints and enforce window management properties specified by the
client. One of the comments on the Emacs bug is worth quoting at length here:
> […] the wm-spec defines maximization in quite express terms:
>
> > Maximization is a very old feature of window managers. There was even
> > a ZoomedState in early ICCCM drafts. Maximizing a window should give
> > it as much of the screen area as possible (this may not be the full
> > --------------------------------------
> > screen area, but only a smaller 'workarea', since the window manager
> > may have reserved certain areas for other windows). A window manager
> > is expected to remember the geometry of a maximized window and restore
> > it upon de-maximization. Modern window managers typically allow
> > separate horizontal and vertical maximization.
>
> Emphasis mine. By any reasonable interpretation, the window manager
> should disregard resize increments in resizing maximized windows, and
> indeed as far as I'm aware, KWin's design choices have been emulated by
> no other conforming window manager.
These arguments seem well-supported and persuasive to me, so I am reopening
this bug, which I am able to reproduce with the following setup:
Emacs 29.3
KDE Plasma 5.27.9
KDE Frameworks 5.103.0
Qt 5.15.8
I understand from <https://community.kde.org/Schedules/Plasma_5> that Plasma
5.27 is still under long-term support, and indeed is still shipped by many
distributions, so it would be nice if a fix could be applied.
I have not (yet) been able to reproduce the issue with Plasma 6, but I have not
tested extensively.
--
You are receiving this mail because:
You are watching all bug changes.
