Bug 31340

Summary: Please implement text search across frames (http://www.kurier.at)
Product: [Applications] konqueror Reporter: atrink
Component: khtmlAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED FIXED    
Severity: wishlist CC: aros, bluedzins, ewal, frank78ac, pascal, rackymail
Priority: NOR    
Version: 3.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description atrink 2001-08-22 19:47:24 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           khtml
Version:           3.0 (using KDE 2.2.0 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.4-4GB
OS/Compiler notes: 

A similar bug-report is already reported and
marked "DONE" too but i am absolutely not
able to search within a certain frame
for a particular word.

1. go to http://www.kurier.at
2. klick on "KINO" (on the top below Kurier online)
3. klick on "PROGAMM"
4. klick into the lower-right frame
5. press ctrl-f and search for e.g. "BURG"

--> search string "BURG" not found

What did I wrong?

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 David Joham 2002-03-07 05:51:18 UTC
Flagging as wishlist and changing title to "please implement text search=20
across frames"
=0D
_________________________________________________________=0D
Do You Yahoo!?=0D
Get your free @yahoo.com address at http://mail.yahoo.com=0D
=0D
Comment 2 Maksim Orlovich 2004-11-12 19:17:44 UTC
*** Bug 77695 has been marked as a duplicate of this bug. ***
Comment 3 Frank Reininghaus 2008-12-10 19:24:03 UTC
*** Bug 177397 has been marked as a duplicate of this bug. ***
Comment 4 Egbert van der Wal 2009-03-15 14:28:12 UTC
I second this, Konqueror is not able to find anything when there are frames on a site. Not even after selecting the frame in which the text actually is.
Comment 5 Frank Reininghaus 2009-03-26 20:07:17 UTC
Finding text in frames will work in KDE 4.2.2 :-)
See bug 187475.