https://bugs.kde.org/show_bug.cgi?id=455538
veggero <niccolo.venera...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DOWNSTREAM
Status|CONFIRMED |RESOLVED
--- Comment #3 from veggero <niccolo.venera...@gmail.com> ---
This really is a downstream issue. I think it's fair on our side to consider
that a maximized window will touch the screen borders. The fact that a third
party kwin script forces the maximized window to be floating even when
maximized produces not only this bug, but other ones too, due to the same
assumption (as an example, you loose the window shadow and rounded corners). I
think in this case it's the script which is taking a risky approach.
This wouldn't fix 455323 either. That bug refers to the fact that, when a
window is maximized, there's too much margin around the panel. Adding an option
to not de-float the panel at all wouldn't fix that: most people wouldn't
discover the option and be left with the bigger margins by default, and people
that want less margin would have to disable de-floating entirely.
In the (near) future, I would like the de-floating mechanism to be a bit
smarter, and defloat in other cases too, such as when you have two windows side
by side that occupy all the screen. This could be approached in various ways,
as an example the panel could de-float it there's any window that's directly
touching it. This would (indirectly) fix this bug and alleviate 455323 too
(half of the de-floated margin was added due to the lack of this mechanism).
--
You are receiving this mail because:
You are watching all bug changes.
