Bug 345566 - Panel is ignored by windows when located between two screens
Summary: Panel is ignored by windows when located between two screens
Status: RESOLVED DUPLICATE of bug 323230
Alias: None
Product: plasma4
Classification: Unmaintained
Component: panel (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL: https://img.bi/#/MSi9aoV!FWpARwkO7JJw...
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-27 06:51 UTC by Denis
Modified: 2018-01-23 22:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screen shot of the incorrect behavior (1.43 MB, image/png)
2015-03-27 06:54 UTC, Denis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Denis 2015-03-27 06:51:50 UTC
When desktop is stretched among two monitors (one on the left another on the right) and the panel is located vertically between two screens (e.g. on the left edge of the right screen), maximized windows ignore the panel. Windows are stretched filling the whole area of the screen and part of it is going under the panel (see the link with the screen shot).

The behaviour is like when panel visibility is set to "Windows go below", however it's set to "Always visible".

This doesn't happen when the panel is placed on the desktop's edge not screen edge (e.g. on the right side of the right screen). 



Reproducible: Always


Actual Results:  
Maximized windows go under the panel.

Expected Results:  
Maximized windows dos not go beyond the panel edge.
Comment 1 Denis 2015-03-27 06:54:41 UTC
Created attachment 91768 [details]
screen shot of the incorrect behavior
Comment 2 Denis 2015-03-27 06:59:14 UTC
KDE version is  4.11.16-3.fc21, couldn't test this on other distros. Bug existed in previous KDE minor version (don't remember which one it was),  but is seems that all 4.11 versions are affected, regardless of disto.
Comment 3 Nate Graham 2018-01-23 22:15:59 UTC

*** This bug has been marked as a duplicate of bug 323230 ***