Bug 255024 - in-page search does not work for the current string
Summary: in-page search does not work for the current string
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (other bugs)
Version First Reported In: 4.11.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-23 10:47 UTC by Christopher Yeleighton
Modified: 2024-05-06 18:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2010-10-23 10:47:23 UTC 
Version:           0.8 (using KDE 4.4.4) 
OS:                Linux

The current search string for a previous page does not work for searching in the next page.

Reproducible: Always

Steps to Reproduce:
1. 
Display the page "Welcome to KDE" [1]

2.
Search for string "K" in the current page.

3. 
Follow the link to the Next page.

4. 
Search for the next occurrence of the current search string.

Actual Results:  
1. <URL:help:/khelpcenter/index.html>
3. <URL:help:/khelpcenter/welcome-to-kde.html>
4. Nothing happens.

Expected Results:  
4. 
KHelpCenter should mark and reveal all occurrences of the string "K" on the page, one after another.

OS: Linux (x86_64) release 2.6.34.7-0.4-desktop
Compiler: gcc

Workaround: retype the "K".
Comment 1 Luigi Toscano 2014-03-13 22:07:05 UTC 
The findbar comes from the khtml component and this behavior can be seen in konqueror/khtml too. Reassigning.
Comment 2 Christoph Cullmann 2024-05-06 18:38:39 UTC 
Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann