SUMMARY It has been very annoying for a long time that the search results in a PDF document show up in the same color as the yellow highlighter. STEPS TO REPRODUCE 1. Take a PDF file, highlight some text with the yellow highlighter 2. Use Find function to search for a term that is within the previous highlighted text 3. Voila, you cannot easily see the search result anymore Solution: A unique color not otherwise available for e.g. highlighting ought to be chosen to highlight Find/search results OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Several people complained about this. All we got so far, is a black border. A discussion about this is in Bug 384267. Also look at: https://phabricator.kde.org/D18238 (why not continue this?) https://phabricator.kde.org/D7662 https://phabricator.kde.org/search/query/Boo2YVUCQ.00/#R *** This bug has been marked as a duplicate of bug 237014 ***
(In reply to David Hurka from comment #1) > https://phabricator.kde.org/D18238 (why not continue this?) From what I've seen, the main reason is that other readers don't do that. Also, it became a little bit clustered ( This could be easily fixed by moving it into settings) One of the main reasons people use KDE is customization, so maybe having this option would be acceptable, and even better. Of course there's other solutions, like getting the system background color, I've thinkered with that but I couldn't get the system color.
To define it as a duplicate does not resolve this annoying issue that has existed for quite some time now. I find this extremely lazy to do such a thing Please fix this issue finally!!!! I propose to use light purple to mark found search terms. And since we are at the Find function, please also include a count of all found terms in document Thanks!
Defining the bug as a duplicate of another bug does not mean that the issue has been resolved, but that the issue has been reported earlier and that the discussion is already happening in the previously-reported bug. So please continue the discussion in the other bug. *** This bug has been marked as a duplicate of bug 237014 ***