Bug 294520 - Pressing F3 to search again searches from the last match, not the current page
Summary: Pressing F3 to search again searches from the last match, not the current page
Status: RESOLVED DUPLICATE of bug 203398
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.14.80
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-20 18:59 UTC by Thiago Macieira
Modified: 2012-08-09 22:12 UTC (History)
2 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 Thiago Macieira 2012-02-20 18:59:43 UTC
Version:           0.14.80 (using Devel) 
OS:                Linux

When you press F3 to search again for a string, Okular searches from the last point where a match was found, instead of searching from the current page. This can be quite annoying if you have changed pages (continued reading) after the last match, as Okular will jump back to where you had been.

In most text editors, the Find Again feature finds from the current position.

Note that this feature is not related to the option "Find from current page" being enabled. In fact, that feature is weird: where would it find from if not the current page? The only other option is from the first page, which should be the name of the feature.

Reproducible: Always

Steps to Reproduce:
1. Open a document in Okular with multiple pages (I've only tested PDF)
2. Ctrl+F and type a string that appears in many pages
3. Press Enter
4. Scroll down, making sure you end up at least one page after the next match of the same string
5. Press F3

Actual Results:  
Okular jumps back to the match that was skipped over

Expected Results:  
Okular continues the search from the current view position

OS: Linux (x86_64) release 3.2.6-3.fc16.x86_64
Compiler: gcc
Comment 1 Simon 2012-08-07 08:03:57 UTC
This appears to be related to the bug 203398.
Comment 2 Albert Astals Cid 2012-08-09 22:12:24 UTC

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