Bug 478773 - In Plasma 6 when you set panel spacer to not expand and its width to 0, the spacer becomes invisible
Summary: In Plasma 6 when you set panel spacer to not expand and its width to 0, the s...
Status: RESOLVED DUPLICATE of bug 478772
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel Spacer widget (show other bugs)
Version: master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-12-20 13:59 UTC by Alex Čižinský
Modified: 2023-12-20 14:53 UTC (History)
1 user (show)

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


Attachments
Wrong image (2.32 MB, image/png)
2023-12-20 13:59 UTC, Alex Čižinský
Details
Plasma 5 behavior (2.37 MB, image/png)
2023-12-20 13:59 UTC, Alex Čižinský
Details
Plasma 6 behavior (2.48 MB, image/png)
2023-12-20 14:01 UTC, Alex Čižinský
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Čižinský 2023-12-20 13:59:31 UTC
Created attachment 164318 [details]
Wrong image

SUMMARY
In Plasma 6 when you set panel spacer to not expand and its width to 0, the spacer becomes invisible, 
it is there but it is like 1px thick, resulting in it being very hard to click on.

In Plasma 5 when it is set like this, the applet has some width.

STEPS TO REPRODUCE
1. Add spacer to a panel
2. Set it to not expand
3. Set its width to 0

OBSERVED RESULT
The applet is almost invisible, as its like 1px thick

EXPECTED RESULT
The plasma 5 behavior.
Where even if the applet's width is set to 0 it has some width.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 5.91.0 (6.0 Beta 2) -> compiled from master using kdesrc-build
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Comment 1 Alex Čižinský 2023-12-20 13:59:58 UTC
Created attachment 164319 [details]
Plasma 5 behavior
Comment 2 Alex Čižinský 2023-12-20 14:01:29 UTC
Created attachment 164321 [details]
Plasma 6 behavior
Comment 3 Marco Martin 2023-12-20 14:53:20 UTC
same cause and same solution to 478772

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