Bug 348660 - Color definitions for tab elements are wrong
Summary: Color definitions for tab elements are wrong
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kwidgetsaddons
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Christoph Feck
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-06-03 19:10 UTC by john
Modified: 2018-10-27 02:16 UTC (History)
1 user (show)

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


Attachments
Wrong color definitions in Kile (149.23 KB, image/png)
2015-06-05 19:32 UTC, john
Details

Note You need to log in before you can comment on or make changes to this bug.
Description john 2015-06-03 19:10:04 UTC
The colors for the sidebar tabs ("Symbols", "Structure", ...) are not set to the proper color scheme values. It appears that the font color for the tabs is set to "button text", whereas the tab background is set to "window background". I have a custom QtCurve scheme, in which the window background is much darker than the buttons. Consequently, window font color is set to white, while button font color is set to black. This leads to the sidebar tabs having black text on dark background, which is unreadable.

The same holds for the tabs at the bottom (console etc.).

Possible fix: Don't mix color definitions for unrelated elements. Instead, set the values to "Window background" and "Window text", or alternatively "Button background" and "Button text".

Reproducible: Always
Comment 1 john 2015-06-05 19:32:18 UTC
Created attachment 93030 [details]
Wrong color definitions in Kile
Comment 2 Christoph Feck 2015-06-16 21:31:26 UTC
Bug is in KMultiTabBar.
Comment 3 Christoph Feck 2016-06-18 03:05:40 UTC
Which widget style are you using? Can you please try running kile from command line with different "-style" arguments, such as "-style Fusion" or "-style Breeze"? It might be an issue with the widget style.
Comment 4 Christoph Feck 2016-07-13 20:20:11 UTC
If you can provide the information requested in comment #1, please add a comment.
Comment 5 Andrew Crouthamel 2018-09-26 22:19:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:16:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!