Bug 250366 - Cursors stop working while adding recipients
Summary: Cursors stop working while adding recipients
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: Git (master)
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: reproducible
Depends on:
Blocks:
 
Reported: 2010-09-06 15:40 UTC by karaluh
Modified: 2017-01-07 21:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description karaluh 2010-09-06 15:40:25 UTC 
Version:           1.13.5
OS:                Linux

Autocomplete list looses focus after adding 4 recipients. Regression introduced in 4.5.0

Reproducible: Always

Steps to Reproduce:
1. Create two contacts with name test1 and test2.
2. Compose new e-mail,
3. start typing word "test",
4. choose one of the contacts using cursors.
5. Repeat points 3 and 4 four times

Actual Results:  
When adding 5th receipient autocomplete list looses focus. It's impossible to choose contact from the list using keyboard

Expected Results:  
The opposite.

OS: Linux (i686) release 2.6.32-0206321505-generic
Compiler: cc
Comment 1 Christophe Marin 2012-01-08 00:58:01 UTC 
Valid in master,

- Open the kmail composer,
- type a letter to trigger the 'Recent addresses' completion,
- use arrows to select a recipient
After 4 recipients, the arrow down key sets the focus on the subject field
Comment 2 Laurent Montel 2012-01-16 18:13:23 UTC 
I confirm it Will look at it soon
Comment 3 Denis Kurz 2016-09-24 18:00:49 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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:42:54 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.