Bug 481749 - Multiple panels on same screen edge shouldn't "stack" if not overlapping
Summary: Multiple panels on same screen edge shouldn't "stack" if not overlapping
Status: RESOLVED DUPLICATE of bug 477939
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.93.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-24 07:17 UTC by Doug
Modified: 2024-02-24 16:37 UTC (History)
2 users (show)

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


Attachments
Image showing the panels each on a different horizontal plane (2.82 MB, image/png)
2024-02-24 07:17 UTC, Doug
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Doug 2024-02-24 07:17:24 UTC
Created attachment 166052 [details]
Image showing the panels each on a different horizontal plane

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Add a panel on a screen edge (top in my case), make it fit content and center it, add a widget
2. Add another panel on that same edge, make it fit content, anchor it to left, add a widget
3. Add a third panel on that same edge, make it fit content, anchor it to right, add a widget

OBSERVED RESULT
Panels each occupy their own horizontal plan, as if they were stacked on top of each other

EXPECTED RESULT
Panels that don't overlap should be able to be on the same horizontal plane (preferably the screen edge)

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Pro WX 3200 Series
ADDITIONAL INFORMATION
Comment 1 fanzhuyifan 2024-02-24 16:37:59 UTC

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