Bug 239026 - When KFind starts, focus is not on "Named" but on Find.
Summary: When KFind starts, focus is not on "Named" but on Find.
Status: RESOLVED FIXED
Alias: None
Product: kfind
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 215046 244544 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-27 17:31 UTC by Földes László
Modified: 2010-07-14 14:55 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 Földes László 2010-05-27 17:31:22 UTC
Version:           2.0 (using KDE 4.4.2) 
OS:                Linux

When Kfind starts (either from Dolphin, Kickoff, or from terminal) the initially focused window element is the Find button. This is not useful for 2 reasons:
1. the user has to click into the "Named" field to enter the search string
2. the default action is "Find" anyway, so the user can press Enter anywhere in KFind window, therefore it is not necessary to put the focus on this button.

Reproducible: Always

Steps to Reproduce:
Start KFind.

Actual Results:  
Focus is on "Find".

Expected Results:  
Focus is on "Named" field (which seems to be a typo, but that goes for another bug report)
Comment 1 Anselmo L. S. Melo (anselmolsm) 2010-05-28 04:25:57 UTC
SVN commit 1131315 by amelo:

Set focus on "named" field when kfind starts instead of the "Find" button.
By setting the initial focus on "named" field, the user does not need to select
it before introducing the search string and, as pointed by the bug reporter,
the default action is "Find", so an 'Enter pressed' triggers the search independently
of the focused widget.

BUG:239026



 M  +1 -0      kfinddlg.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1131315
Comment 2 Anselmo L. S. Melo (anselmolsm) 2010-06-20 05:04:38 UTC
*** Bug 215046 has been marked as a duplicate of this bug. ***
Comment 3 Frank Reininghaus 2010-07-14 14:55:03 UTC
*** Bug 244544 has been marked as a duplicate of this bug. ***