| Summary: | Replaced text is shown black on black | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Valdas <zmogas> |
| Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | 04qw59ty, slartibart70 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/ktexteditor/bb1968631c2931c8a67b5f4bfc92a0553d00bc83 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
| Attachments: | Screenshot of Kate's black on black highlight. | ||
|
Description
Valdas
2016-05-23 16:45:47 UTC
Created attachment 99146 [details]
Screenshot of Kate's black on black highlight.
Please adapt your color scheme: Whenever we replace text, the text color of the highlighted matches now uses the default text color (which is black in your case). Did you change the search & replace background colors? To my understanding you did, since the defaults are rather geenish or yellowish - is that correct? This change was done to get better contrast, since it is hard to find a background color that matches all different foreground color text can have. Now, the foreground color is always the default text color in case a search & replace highlight is visible. Oh damn, you are correct. A bug slipped in that sets the background color to the foreground color, which in turn leads to the bug you reported. A review request to fix this is here: https://git.reviewboard.kde.org/r/128035/ Git commit bb1968631c2931c8a67b5f4bfc92a0553d00bc83 by Dominik Haumann. Committed on 28/05/2016 at 16:29. Pushed by dhaumann into branch 'master'. Search & Replace: Fix replace background color (regression introduced in v5.22) REVIEW: 128035 M +1 -1 src/search/katesearchbar.cpp http://commits.kde.org/ktexteditor/bb1968631c2931c8a67b5f4bfc92a0553d00bc83 *** Bug 363681 has been marked as a duplicate of this bug. *** *** Bug 368032 has been marked as a duplicate of this bug. *** |