Bug 221011 (uga) - Oxygen window decoration does not follow text color setting
Summary: Oxygen window decoration does not follow text color setting
Status: CONFIRMED
Alias: uga
Product: Oxygen
Classification: Plasma
Component: win deco (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-02 19:12 UTC by Unai Garro
Modified: 2021-03-09 23:58 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unai Garro 2010-01-02 19:12:30 UTC
"Active Titlebar Text" and "Inactive Titlebar Text" color settings are not followed by oxygen, so when a dark color is used for the background and a white text is chosen, the text remains black, and it's not readable.

Screenie here: http://imagebin.org/77966
Comment 1 Unai Garro 2010-01-02 19:16:31 UTC
Forgot mentioning, this is true for KDE v. 4.3.85, which I am unable to choose in the version list.
Comment 2 Hugo Pereira Da Costa 2010-01-05 03:21:40 UTC
mmm. Its actually somewhat more complicated. 
The title text is actually drawn on top of the active window titlebar background only in case of tabbing, and only for inactive tabs (as illustrated in the screenshot), this because whatever settings you use, the active tab title text is always drawn on top of the "window background" color (and not the active titlebar color), which is a design choice. (we want the active title to be part of the main window, and blent with it). 

So that the color you would need is an "inactive text on active background", which as far as I know, does not exists in kde color scheme. 

Now: I agree that the situation in the screenshot is not acceptable. 
I'm working on deriving the proper "inactive text" color to make this work ...
Comment 3 Justin Zobel 2021-03-09 23:58:22 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.