Bug 437289 - Oxygen plasma style: unreadable white text on white background
Summary: Oxygen plasma style: unreadable white text on white background
Status: RESOLVED DUPLICATE of bug 438854
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.21.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2021-05-18 06:00 UTC by Antonio Orefice
Modified: 2021-08-31 18:18 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Orefice 2021-05-18 06:00:51 UTC 
When switching to oxygen plasma style, the text in krunner or in the main menu is unreadable, because the background of the input box and the text itself are white.


STEPS TO REPRODUCE
1. switch to oxygen plasma style
2. write something in krunner

OBSERVED RESULT
can't see anything


EXPECTED RESULT
see something



ADDITIONAL INFORMATION
It is not oxygen only, other dark themes which still uses white background for input boxes are broken as well (oxylight or oxylighter from kde-store).
So i suspect something has been changed lately in the plasma style engine(?).

however there are other cases when the text is still readable (for example the size of the panel when entering in configuration mode is still readable - black over a white background).
Comment 1 Antonio Orefice 2021-05-18 06:12:11 UTC 
It seems that some plasma elements

obey to:
[Colors:View]
BackgroundNormal

But Ignores:
[Colors:View]
ForegroundNormal
Comment 2 Nate Graham 2021-05-19 02:22:12 UTC 
Marco, any ideas here?
Comment 3 Alberto Mattea 2021-06-17 14:06:16 UTC 
I'm experiencing this too, with another theme (Breeze Krystal Light).

It seems that the text in most textboxes gets controlled by Colors:Window ForegroundNormal instead of Colors:View ForegroundNormal as it should be.
Comment 4 Nate Graham 2021-08-31 18:18:26 UTC 

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