Bug 304359 - kaddressbook-4.8.3 does not allow dead accents to be typed into "Custom Name" when contact is new
Summary: kaddressbook-4.8.3 does not allow dead accents to be typed into "Custom Name"...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-31 21:42 UTC by Christian
Modified: 2017-01-07 22:15 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian 2012-07-31 21:42:48 UTC
kaddressbook-4.8.3 does not allow dead accents to be typed into "Custom Name" when contact is new.

Reproducible: Always

Steps to Reproduce:
1. Create a new contact. The window for entering the contact details opens.
2. Choose "Custom" from the Display name dropdown
3. Try to enter a letter that is typed with a dead accent, e.g. ú (' followed by u).
Actual Results:  
The letter is not written.

Expected Results:  
The letter should be written.

It works with foreign letters that are on the keyboard, e.g. ä, if you enter them as one key press. But it doesn't work if you try to enter it with two key presses, e.g. as " followed by a.
Also, it works totally fine once the contact has been saved. When you edit an existing contact, the typing works.
Comment 1 Laurent Montel 2012-08-01 06:54:43 UTC
I confirm it.
I work after that you focus out focus in.

It's a kcombobox perhaps there is a bug into.
Comment 2 Denis Kurz 2016-09-24 20:53:00 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 22:15:43 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.