https://bugs.kde.org/show_bug.cgi?id=437089
Anthony Fieroni <bvb...@abv.bg> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bvb...@abv.bg
--- Comment #34 from Anthony Fieroni <bvb...@abv.bg> ---
(In reply to Nate Graham from comment #33)
> Not fixed; this requires one of two things to be done to fix it:
> 1. KWin interprets "open window at maximum size" to be equal to "open window
> in maximized state" on Wayland as it does on X11
> 2. All apps exhibiting this problem are changed to request opening in the
> maximized state rather than at the maximum window size
>
> So far KWin devs are not convinced that #1 is appropriate, and #2 has not
> been done yet even for KDE's own apps, so the problem is not fixed.
I think 1. is sufficient because there is no meaning of maximize size without
maximize state, i.e. no difference from user's perspective. Actually same
applies to all other windows state like KWin positioning when touch edge 1/4,
1/2 i.e. when the size match a predefined state it should activate it.
Actually there is (was) a problem in X11, (I'm not use it for few years) but
when restart 1/2 window, it could start on its normal state (which is not 1/2
just random size), I investigate in the problem and came with conclusion
especially difference between KWin sets normal state of the window which read
from config its normal coordinates and size, but instead KWin should activate
1/2 state. In other hand the app (Kate) doesn't well store and read its state.
--
You are receiving this mail because:
You are watching all bug changes.
