Bug 454654 - When using dark accent colors in window titlebar, some text elements fail to automatically switch to light colors as most others do
Summary: When using dark accent colors in window titlebar, some text elements fail to ...
Status: CONFIRMED
Alias: None
Product: Breeze
Classification: Plasma
Component: QStyle (show other bugs)
Version: 5.24.90
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: usability
: 455411 460627 462205 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-05-31 11:31 UTC by Mateus Melchiades
Modified: 2022-11-30 04:28 UTC (History)
9 users (show)

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

Attachments
Example of poorly visible text (253.64 KB, image/png)
2022-05-31 11:31 UTC, Mateus Melchiades 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mateus Melchiades 2022-05-31 11:31:11 UTC 
Created attachment 149355 [details]
Example of poorly visible text

SUMMARY
When I choose to use accent color from my wallpaper, the resulting color is a dark shade of gray (#54636b) which causes most text elements in application headers to become white. However, some elements like the "Install" button in discover or the menu bar in Kate still use a dark font, which makes them hard to see.


STEPS TO REPRODUCE
1. Set accent color to a dark color
2. Tint application headers with accent color
3. Observe difference in font color between elements

Linux/KDE Plasma: Fedora Kionite 36
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Comment 1 Nate Graham 2022-06-01 18:12:31 UTC 
Can reproduce; most colors change so I think this may actually be a Breeze QStyle issue.
Comment 2 Nate Graham 2022-06-16 19:57:48 UTC 
*** Bug 455411 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2022-10-18 18:47:06 UTC 
*** Bug 460627 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2022-11-30 04:28:59 UTC 
*** Bug 462205 has been marked as a duplicate of this bug. ***