maemo.org Bugzilla – Bug 5633
No hint that it is impossible to paste an strings containing non-numeric characters into a phone number field
Last modified: 2010-01-14 12:28:04 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1. Open a skype (or other) chat
2. Write: "Mobile phone: +123456789987"
3. Press the send button
4. Tip and hold onto the number you wrote in step 2 in the chat protocol. A
context menu will appear.
5. Select "copy".
6. Open a contact
7. select "edit contact". The contact is getting editable.
8. select "add field"
9. select one of the phone number fields
10. Try to insert the phone number from step 5 using the keys [Ctrl] + [v]
1. An error message occurs because in step 5 not only the whole number but the
complete line of text (remember: "Mobile phone: +123456789987") was copied in
step 5. There was no possibility to select only a part of the text.
2. The complete string will be inserted but the user has to correct the sting
(numbers and '+' only) if he wants to save the contact.
Nothing happens. The user doesen't know whats going on.
An a little bit better solution would be to inform the user that he could not
insert strings including non-numeric characters. But than the user has to
understand that the whole line was copied in step 5 and not only the number.
I came across this when trying to clean up my imported contacts (interestingly
those are allowed to have non-numeric characters in phone fields) a bit: copy
a number that included spaces from wrong field, try to paste it into right one,
Another suggestion would be to filter out the non-allowed characters and paste
the rest, eg "+123456789987" in the above example.
AFAIK the copy-and-paste issue is in hildon-input-method.
The fix is underway.
This has been fixed before the internal build version 2009.44-5 was released.
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
Fixed in Firmware PR 1.1.
(Version field is for the version in which the bug still occurs. Resetting.)
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update