GNOME Bugzilla – Bug 506024
copying autocompleted addresses between to/cc fields results in invalid address
Last modified: 2008-08-26 14:47:32 UTC
Please describe the problem: copying autocompleted addresses between to/cc fields results in invalid address. Steps to reproduce: 1. Input an address with autocompletion in "cc" field. 2. Copy the address with "Ctrl+c" 3. paste the address to "to" field, using "ctrl+v" 4. delete the address in "cc" field, only keep "to" field. Actual results: No receipt is found. Expected results: Copying address can be recognized correctly. Does this happen every time? Yes. Other information:
Created attachment 101720 [details] Screenshot The address in "CC" field is underscored, but copying one in "TO" field isn't recognized by short-key "ctrl+c/ctrl+v".
Created attachment 101721 [details] [review] Possible patch Show the email address as well as name when autocompletion is successful. So that shot-key "ctrl+c/ctrl+v" is valid.
Simonz, the patch seems to be corrupted. Also we now have a r-click (Copy/Cut Contact). I'm not infavour of showing the full text. If there is a way to attach a callback to copy/paste, it might be great.
Created attachment 102032 [details] [review] Possible fix Srag, it might be a good idea to add a function like what right-click menu and bind to "copy-clipboard" signal of gtkentry. But I'm afraid it's difficult to deal with the following case. - Aussume "jeff.cai, simon.zheng," are both autocompleted correctly. - Select "jeff.cai, simon" and press "ctrl+c" - Move to naother field, press "ctrl+v" - Only last contact is autocompleted correctly. "jeff.cai" is missing. I think full text is more suitable for this case. Do you have any idea?
Simonz, when we have a call back, you can copy the right things based on the selection I feel. If You can get the selected text, from thhat you can get the emails from the model and modify the selected text in the clipboard IMHO I'm not in favour of this patch.
Set the wrong status last time.
Bumping version to a stable release.
*** This bug has been marked as a duplicate of 207728 ***