Created attachment 102530 [details] Find in document, matches found When searching for text inside a document (Ctrl+F) the text inside the search / find box becomes unreadable when using a dark UI theme (see screenshots). The reason for this is that the background color is changed to either a light green or light red, but the text color is the default theme color. This works for bright themes with black text, but not at all for dark themes with white text.
Created attachment 102531 [details] Find in document: no matches found
Changing product to frameworks-ktexteditor, the issue is there.
It works for me for Breeze Dark, so I cannot reproduce. Which color scheme do you use exactly? For me, the green and red are very dark, so readability is very good compared to your example. So from my perspective, this is fixed...? Please also try again with KDE Frameworks 5.31.
I'm using the latest Git revision of KDevelop/KDevplatform on KF 5.30. I have the issue with both the Breeze Dark theme as well as the Krita Dark theme by David Revoy.
This only happens when switching color-scheme at runtime from within the application, fix should be this: https://phabricator.kde.org/D4637
No, it does not. This is permanent.
Did you select the color scheme in KDevelop's Settings menu or in systemsettings?
I did set it in the application. So if with "runtime switching" you also mean the program restoring the color theme at startup, then your observation is correct. The problem, however, is not that I changed the setting at runtime and it would be gone after a full restart (like those artifacts that often appear when switching Plasma themes where certain UI elements keep their old appearance until I restart my session).
Yes, sorry, bad phrasing from my side; still the issue addressed in the linked RR.
To clarify what I meant, setting it in the application still switches "at runtime", just automatically at each startup, and thus has the same issue in this case.
In this case, this is a duplicate of bug #373764, right ?
Yes. Marking this as duplicate as the other one contains more specific information. *** This bug has been marked as a duplicate of bug 373764 ***