Bug 408187

Summary: Sidebar text is always considered active from the perspective of applying inactive window effects
Product: [Applications] systemsettings Reporter: Nate Graham <nate>
Component: sidebarviewAssignee: Marco Martin <notmart>
Status: RESOLVED FIXED    
Severity: minor CC: bugseforuns, kde
Priority: NOR    
Version: 5.14.90   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=408191
Latest Commit: Version Fixed In:
Attachments: System Settings sidebar faded text when the window is active

Description Nate Graham 2019-06-01 21:27:41 UTC
Created attachment 120483 [details]
System Settings sidebar faded text when the window is active

STEPS TO REPRODUCE
1. Go to System Settings > Colors
2. Edit the current color scheme
3. Check "Apply Inactive window effects"
4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right
5. Open System Settings

OBSERVED RESULT
The sidebar text is always faded no matter if the window is inactive or not


EXPECTED RESULT
The text should only be faded when the window is inactive


SOFTWARE/OS VERSIONS
Everything from git master
Comment 1 Christoph Feck 2019-06-25 15:34:27 UTC
Does systemsettings use the same Kirigami Drawers as bug 408191?
Comment 2 Nate Graham 2019-06-26 11:59:44 UTC
It does use Kirigami components, but not specifically the same drawer component. Not sure whether it would be fixed automatically with the fix for bug 408191.
Comment 3 Patrick Silva 2020-02-12 23:30:04 UTC
cannot reproduce on my system.

Operating System: Arch Linux 
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Comment 4 Nate Graham 2020-02-13 01:30:25 UTC
Hmm I can still reproduce the opposite effect: now sidebar text is always considered active, not inactive.

Also, Discover's sidebar is just fine; only System Settings is affected in this way.
Comment 5 David Edmundson 2021-04-14 11:13:30 UTC
I did a fix with palette issues in system settings in ef525ffd3ee4d9da1ae481b435ef4da571594b4d (5th Jan) 

Cannot reproduce as per original instructions.

Please reopen if it's still an issue
Comment 6 Nate Graham 2021-04-14 13:28:52 UTC
Seems like this is fixed now, thanks!