GNOME Bugzilla – Bug 750375
Text selection is unreadable when a line is selected by double-clicking in the margin
Last modified: 2017-07-10 12:31:58 UTC
There is a bug in evince 3.16.1-1 on Arch using the Gtk theme numix-frost-light. When selecting a section of black on white text, the text is rendered white and the selection highlighting background blue. But when selecing a line for highlighting the text appears grey and is unreadable. However, this only happens when selecting the line by double-clicking the right margin, but not when double-clicking the left margin, in which case the highlighting is correct. screenshot of the right behaviour: https://userpage.fu-berlin.de/~danielro/correct-highlighting.png and of the wrong: https://userpage.fu-berlin.de/~danielro/incorrect-highlighting.png (In them the colours aren't quite true, but the important features come out.) The document used is https://userpage.fu-berlin.de/~danielro/charity_simple-comments_RB.pdf
Could this be an issue in the theme?
I just tried several gtk themes (adwaita, high contrast, numix, arc) and the behabiour was consistent (that is on 3.18.0 now)
Thanks for the update. I am closing this bug as obsolete.
sorry for the ambiguity, i mean consistently between themes but broken
Ok, I see the issue now. It has nothing to do the annotations, only with the way you select a line: 1. If you select a line within the boundaries of text, it works as expected. 2. If you select a line by double-clicking outside the boundaries (margin) of the text, you get a rectangle hiding the text.
Curiously, the odd behaviour happens when double-clicking on the right side. On the left side works well.
This is actually a bug in poppler (the library used by Evince to render PDF). Trying the same thing with poppler-glib-demo, the behaviour is the same. Please, may you file a bug in poppler' bugzilla? https://bugs.freedesktop.org/enter_bug.cgi?product=poppler
The document is no longer available. Did you file the bug in Poppler? (I cannot find it).
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!