Bug 110105 - After searching for files containing text curser focus jumps from visable tab to NAme/Location Tac
Summary: After searching for files containing text curser focus jumps from visable tab...
Status: CONFIRMED
Alias: None
Product: kfind
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2005-08-03 17:25 UTC by Mike Z
Modified: 2021-03-09 23:51 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed 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 Mike Z 2005-08-03 17:25:12 UTC 
Version:            (using KDE KDE 3.3.2)
Installed from:    Mandriva RPMs
Compiler:          GCC 3.4.3 
OS:                Linux

Click ON tools find file. Click on the contents tab and enter a string to search for in containing text. Click on find or press enter and notice the cursor is no longer in the containing text box. If you start typing and look on the Name Location tab you will see that the Named box has the text in it.
Comment 1 Philip Rodrigues 2006-09-05 23:17:40 UTC 
Confirmed on 3.5 branch r575787. A little confusing, since the focus changes to a widget that isn't visible.
Comment 2 FiNeX 2008-05-05 00:07:49 UTC 
Cannot reproduce on 3.5.9 AND 4.1 (trunk r802881).
Comment 3 Linus Östberg 2008-05-14 11:39:59 UTC 
Confirmed in 3.5.9, can't find where to search for files in trunk (r807429).
Comment 4 FiNeX 2008-05-14 12:06:30 UTC 
Linus: you can manually start kfind.
I don't know what I've tested nine days ago... anyway actually a can reproduce the bug even on trunk...
Comment 5 Dario Andres 2010-02-19 00:05:44 UTC 
Still valid on KDE SC 4.5 (svn rev. 1092352)
Comment 6 Justin Zobel 2021-03-09 23:51:08 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.