Bug 348223 - Search does not begin from current page.
Summary: Search does not begin from current page.
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 0.20.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 349940 350106 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-05-25 22:12 UTC by Stephen Bosch
Modified: 2015-07-11 08:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Bosch 2015-05-25 22:12:28 UTC
When I try to search in the matplotlib PDF manual, searches always begin from the beginning of the document, even if I select the page I want to start at. It does not matter how I select it -- through the table of contents, through clicking on the page directly, by using the pager, or by entering the starting page number directly in the pager.

Reproducible: Always

Steps to Reproduce:
1. Download the matplotlib user's guide here: http://matplotlib.org/1.4.3/Matplotlib.pdf
2. Go to any point in the document with okular.
3. Perform a search using CTRL-F.

Actual Results:  
The search ignores the current page and begins searching at the start of the document.

Expected Results:  
The search should start at the active page.
Comment 1 Albert Astals Cid 2015-05-26 05:20:43 UTC
Have you unmarked the "From current page" in the options menu of the search bar by any chance?
Comment 2 Stephen Bosch 2015-05-26 07:58:46 UTC
My apologies -- I had looked at the settings in an attempt to resolve this but I'm using a localized version, and didn't recognise the option. It was indeed unchecked. The search is working as expected.

Thanks for the quick response and the hint!
Comment 3 David Edmundson 2015-07-09 10:23:21 UTC
*** Bug 349940 has been marked as a duplicate of this bug. ***
Comment 4 David Edmundson 2015-07-11 08:58:53 UTC
*** Bug 350106 has been marked as a duplicate of this bug. ***