After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358955 - "X found on this page" doesn't work correctly, search the entire document instead
"X found on this page" doesn't work correctly, search the entire document ins...
Status: RESOLVED DUPLICATE of bug 343199
Product: evince
Classification: Core
Component: general
0.6.x
Other All
: Normal minor
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-02 10:24 UTC by Alexander van Loon
Modified: 2006-10-02 23:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Screenshot of Evince (252.95 KB, image/png)
2006-10-02 10:27 UTC, Alexander van Loon 		Details

Description Alexander van Loon 2006-10-02 10:24:09 UTC 
Sometimes Evince says it has "0 found on this page" while it did in fact find the search term, and jumped to and highlighted the found word. Sometimes i don't see the highlighting and I only notice the "0 found on this page", and I miss stuff in documents.

And sometimes I'm not interested at all how much Evince has found on the current page, I want to know how much it has found in the entire document instead. for example, the search result could be modified to "3 found on this page, 8 found in the document"

Other information:
Comment 1 Alexander van Loon 2006-10-02 10:27:48 UTC 
Created attachment 73837 [details]
Screenshot of Evince

As you can see it displays "0 found on this page" while it did find one result (notice highlighted result on the first line visible on page 9). Maybe it's trying to say it found zero results on page 10, while a smaller part of page 9 including the search result is still visible? Whatever it is, it's very confusing and I assume this screenie makes that clear.
Comment 2 Nickolay V. Shmyrev 2006-10-02 23:59:22 UTC 
Yes, it's another side of a known problem, let's track it's state in earlier bug.

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