Bug 252903 - Wrong characters displayed in recipients tab of the Composer
Summary: Wrong characters displayed in recipients tab of the Composer
Status: CLOSED DUPLICATE of bug 248391
Alias: None
Product: KMail Mobile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-30 22:24 UTC by Sabine Faure
Modified: 2011-01-21 22:00 UTC (History)
1 user (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 Sabine Faure 2010-09-30 22:24:13 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

If the user types an email address in the Composer recipients tab, blue characters appears instead of white ones whereas the blue arrow was never hold.

This is annoying because if you type fast you realize the mistakes only afterwards and have to go back to fix them.

This should not happen.

Reproducible: Always

Steps to Reproduce:
- Launch Kmail-mobile
- Click on 'Write new email' button
- Open the 'Recipients' tab
- Type in a long email address all in one go (ex: sabinetest@kdab.com)

Actual Results:  
The recipients line edit displays: s*b8n3tes5@kdab.com eventhough the user never touched the blue arrow key.

The symbols/numbers characters are not always in the same spot but they are always somewhere in the typed email address.

Expected Results:  
This should not happen. There is no reason for the symbols/numbers to be displayed when the user does not press the blue arrow key.

N900,  4:4.5~20100930.1181183-1maemo1.1180919
Comment 1 Volker Krause 2010-10-01 08:58:15 UTC 

*** This bug has been marked as a duplicate of bug 248391 ***
Comment 2 Sabine Faure 2010-10-01 18:19:15 UTC 
Hi Felix!

I am changing back the status of this bug from closed duplicate to resolved duplicate because I usually retest them once the original bug is corrected in case it does not fix the duplicate.

Since bug #248391 is not yet corrected I cannot retest and close that one yet.

N900, 4:4.5~20101001.1181533-1maemo1.1181469
Comment 3 Felix Wolfsteller 2010-10-13 19:26:51 UTC 
Closing, as it works fine now (the duplicate is closed, too).
Comment 4 Sabine Faure 2011-01-21 22:00:47 UTC 
Hi Felix!

Thx for closing this bug ;o)

I finally had a chance to retest it today and indeed I cannot reproduce it anymore.

N900, 4:4.6~.20110118.1600.git254268b-1maemo1.121498