Bug 336374

Summary: Panels should not be able to overlap each other
Product: [Plasma] plasmashell Reporter: Philipp Stefan <neptunecat34>
Component: PanelAssignee: David Edmundson <kde>
Status: CLOSED FIXED    
Severity: wishlist CC: 677ee1vp, alex, alxgvr, crissi99, daeron806, k-cottonears, kde, nate, notmart, postix, powerdollkirby, seqularise, tk20
Priority: HI    
Version: master   
Target Milestone: 1.0   
Platform: unspecified   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=375066
Latest Commit: Version Fixed In: 6.2.0
Sentry Crash Report:
Attachments: The menu of the newly created panel is obscured by the old one
New panel overlaping the old
Panel overlapping in Plasma 6
Same panels overlapping each other again in Plasma 6

Description Philipp Stefan 2014-06-18 07:11:30 UTC
Created attachment 87242 [details]
The menu of the newly created panel is obscured by the old one

When one creates a new panel and the new and the old one intersect  then these two can overlap each other depending on which one is focused. For example I have a panel at the bottom of my desktop. When I add another panel on the left screen edge then it is overlapped by the already existing one. This also means that the panel menu is obscured by the first panel, unless I click on the second, new panel first to give it focus. 

I think it would be sensible to not let the newly created panel span across the whole left screen edge on creation.
Comment 1 Philipp Stefan 2014-06-18 07:13:04 UTC
Created attachment 87243 [details]
New panel overlaping the old

The panel menu button can be accessed after giving it the focus by clicking somewhere on the new panel. However, it then overlaps the new panel.
Comment 2 David Edmundson 2014-06-18 09:29:29 UTC
*** Bug 332139 has been marked as a duplicate of this bug. ***
Comment 3 Marco Martin 2014-06-18 10:00:55 UTC
it's almost #332139
It's a thing tough I think any solution would cause far more damages than the problem
Comment 4 David Edmundson 2018-06-09 15:15:04 UTC
*** Bug 289998 has been marked as a duplicate of this bug. ***
Comment 5 Tom 2020-02-20 13:24:08 UTC
Unfortunately this bug still eists.

Has there been any work done to fix it?
Comment 6 David Edmundson 2021-01-28 14:57:12 UTC
*** Bug 372360 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2022-09-09 04:35:27 UTC
*** Bug 458869 has been marked as a duplicate of this bug. ***
Comment 8 AlexDeLorenzo.dev 2024-04-15 03:02:22 UTC
Created attachment 168534 [details]
Panel overlapping in Plasma 6

Still an issue in Plasma 6. I uploaded an example of two panels overlapping.


KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Graphics Platform: Wayland
Comment 9 AlexDeLorenzo.dev 2024-04-15 03:02:59 UTC
Created attachment 168535 [details]
Same panels overlapping each other again in Plasma 6
Comment 10 Filip 2024-05-17 06:33:36 UTC
*** Bug 485901 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2024-06-28 19:21:59 UTC
This is effectively fixed as of Plasma 6.2 now when using "Fill space" mode. Panels using this mode (which is the default one) will avoid overlapping other ones on adjacent screen edges.
Comment 12 Tom 2024-06-29 10:36:48 UTC
(In reply to Nate Graham from comment #11)
> This is effectively fixed as of Plasma 6.2 now when using "Fill space" mode.
> Panels using this mode (which is the default one) will avoid overlapping
> other ones on adjacent screen edges.

You don't believe how happy this makes me to hear! While mostly a visual annoyancy, having a fill space mode was what I have been dreaming of for a long time! Thanks a lot!
Comment 13 Kirby 2024-07-23 19:32:38 UTC
(In reply to Nate Graham from comment #11)
> This is effectively fixed as of Plasma 6.2 now when using "Fill space" mode.
> Panels using this mode (which is the default one) will avoid overlapping
> other ones on adjacent screen edges.

still an issue in 6.1.2 https://i.ibb.co/1mKQtTV/1.png
Comment 14 Nate Graham 2024-07-23 21:16:05 UTC
Like I said, it's fixed in 6.2.

Also your screenshot depicts a different issue: Bug 477939.