Bug 249188

Summary:	When adding a new contact, the Name field should be focussed by default
Product:	[Applications] kaddressbook	Reporter:	Karthik Periagaram <karthik.periagaram>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	anderslund, fest.in, tokoe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Karthik Periagaram 2010-08-27 08:44:05 UTC

Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

When adding a new contact, the dialog opens without any field focussed. Ideally, the 'Name' field should be in focus so that the user can start typing the name straightaway. Otherwise, it takes one more click before I can start entering the contact information.

Reproducible: Always

Steps to Reproduce:
Open the KAddressBook Contact Manager.
Click New Contact.

Actual Results:  
The dialog doesn't focus the 'Name' field, requiring an extra click before entering the data.

Expected Results:  
The dialog should focus the 'Name' field so that the user can enter data without delay.

I think the Address book field is the one in focus, but it's hardly visible because of the oxygen widget style. Without being able to quickly see which field is in focus, the user is left to frantically press Tab to move the focus around. This just causes more delays.

Comment 1 Anders Lund 2011-11-14 12:03:06 UTC

In my case, the addressbook resource selection combo in the top have focus, which is fine because i have more than one.

I think the name field should be in focus if there is only one addressbook, or only one in use (selected).

Comment 2 Denis Kurz 2016-09-24 20:52:59 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 21:31:26 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.