Bug 124615 - Konqueror search report wrong values when there is only one ocurrence of the desired string, if F3 is continuosly pressed
Summary: Konqueror search report wrong values when there is only one ocurrence of the ...
Status: RESOLVED DUPLICATE of bug 118152
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 124888 133199 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-31 05:17 UTC by Camilo Lòpez
Modified: 2008-03-10 16:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of the issue. (12.48 KB, image/png)
2006-04-01 10:18 UTC, Nick Warne
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Camilo Lòpez 2006-03-31 05:17:21 UTC
Version:           3.5.2 (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

When looking for a string inside konqueror ( using konqueror's find feature ) if only ONE ocurrence of the search string is found, then a question dialog pops up asking for an action to take : continue searching or stop, if you press F3 for every time you try to find, the number of occurrences is incremented by one but there is only one ocurrence.
Comment 1 Nick Warne 2006-04-01 10:18:31 UTC
Created attachment 15404 [details]
Screenshot of the issue.

Same here on 3.5.2 built from source.
Comment 2 Philip Rodrigues 2006-04-05 18:22:12 UTC
*** Bug 124888 has been marked as a duplicate of this bug. ***
Comment 3 Thiago Macieira 2006-04-06 16:17:33 UTC
I can reproduce this.
Comment 4 Tommi Tervo 2006-08-29 18:52:39 UTC
*** Bug 133199 has been marked as a duplicate of this bug. ***
Comment 5 Tommi Tervo 2006-08-29 18:54:53 UTC

*** This bug has been marked as a duplicate of 118152 ***
Comment 6 Daniele Primon 2008-03-10 16:53:44 UTC
Same result appear to me. Using konqueror 3.5.8 from debian/unstable. After viewing the source on websvn I guess the issue is originated in khtml_parts.cpp from kdelibs.

The counter keeps increasing each time the document has been cycled for matches. In some circustances it is reset (e.g. on changing an option), but the behaviour is not always congruous.