GNOME Bugzilla – Bug 561487
When using keyboard, email address auto-complete selects wrong address
Last modified: 2008-12-19 10:10:22 UTC
the bug has been described on https://bugs.launchpad.net/bugs/294521 "1. Right click -> send to... 2. press TAB (to focus email field) 3. type 'mar' in the email field 4. use arrow keys to select second 'Maria' in the autocomplete list 5. press enter to select the address 6. press enter again to send the file 7. The first address is filled in in Evolution instead of the one I selected."
Could you please add debug in "contacts_selected_cb" in src/plugins/evolution.c and print out the identifier selected?
the bug doesn't seem to happen for all contacts but when it does the callback is called once using the correct email when pressing entry in the combo list and an another time when pressing enter to validate the dialog and it's using the wrong email on this one
using enter seems to trigger the signal for the selected text entry and for the send button and the bug seems to be a race between those calls
Can confirm, that clicking “Send” button picks up correct email address, pressing an Enter key while in the email address box, picks up incorrect (first from the drop down) email address.
It's a bug in e-contact-entry.
This might be enough to fix it, but eds isn't playing ball and crashes randomly for me. Any chance for you to test this? Index: nautilus-sendto-command.c =================================================================== --- nautilus-sendto-command.c (revision 370) +++ nautilus-sendto-command.c (working copy) @@ -411,8 +411,8 @@ gtk_widget_hide (GTK_WIDGET(w)); ui->contact_widgets = g_list_append (ui->contact_widgets, w); if (GTK_IS_ENTRY (w)) { - g_signal_connect (G_OBJECT (w), "activate", - G_CALLBACK (send_if_no_pack_cb), ui); + g_signal_connect_after (G_OBJECT (w), "activate", + G_CALLBACK (send_if_no_pack_cb), ui); } } }
Closing, reopen the bug if it doesn't fix it. 2008-12-19 Bastien Nocera <hadess@hadess.net> * src/nautilus-sendto-command.c (set_contact_widgets): Try to avoid the handlers internal to the plugin not being run on occasions, as they were racing with the "activate" handler (Closes: #561487)