Closed Bug 1089711 Opened 5 years ago Closed 5 years ago

Recipient autocomplete: after selecting result entry with [cursor down],[cursor right], confirming with TAB or ENTER cunningly selects the wrong recipient (1st result)

Categories

(Thunderbird :: Address Book, defect, critical)

31 Branch
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1107844

People

(Reporter: stampy, Unassigned)

References

Details

(Keywords: privacy, ux-trust)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140923175406

Steps to reproduce:

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

1. Type a letter into "To" field, so autocomplete list shows
2. Press down arrow TWICE, to 2nd result
3. Press right arrow ("To" completes with 2nd result)
4. Press tab (next field gets focus, "To" changes to 1st result)


Actual results:

In step 4, field changes "back" to an address I didn't select.


Expected results:

In step 4, "to" field should stay what I selected in step 2 & 3.

(Thank you volunteer Thunderbird developers!  You Rock!!!)
TB 31.3.0 installed 19/12/2014; Windows 7 Pro;

Confirm above report.
Autocomplete of "to" field offers list; down-arrow to required entry; Tab reverts to first result.

Always reproducible.
New to me with this release.
Brian & djn, thanks 4 reporting/confirming.

This is a keyboard-only variant of bug 1107844, involving [cursor down] and [cursor right](!) for selection of desired contact from autocomplete dropdown results, then upon confirming with tab/enter, results are reverted to 1st match from results list.

Magnus, does your patch in bug 1043310 fix this?

(In reply to djn from comment #1)
> TB 31.3.0 installed 19/12/2014; Windows 7 Pro;
> 
> Confirm above report.
> Autocomplete of "to" field offers list; down-arrow to required entry; [*] Tab
> reverts to first result.

No, only if you also use cursor-right where I added the [*] mark.
Just tabbing out directly after cursor-down keeps the correct address.

> Always reproducible.
> New to me with this release.

Yes.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Depends on: 1107844, 1043310
Ever confirmed: true
Flags: needinfo?(mkmelin+mozilla)
Keywords: privacy, ux-trust
OS: Windows 7 → All
Hardware: x86_64 → All
Summary: Compose recipient autocomplete, tabbing selects the wrong recipient → Recipient autocomplete: after selecting result entry with [cursor down],[cursor right], confirming with TAB or ENTER cunningly selects the wrong recipient (1st result)
Also, just [cursor-right] to select *first* autocomplete suggestion having ">>" should normalize that entry, but currently retains "searchwords >>". Is that covered?
Component: Message Compose Window → Address Book
(In reply to Thomas D. from comment #2)
> This is a keyboard-only variant of bug 1107844, involving [cursor down] and
> [cursor right](!) for selection of desired contact from autocomplete
> dropdown results, then upon confirming with tab/enter, results are reverted
> to 1st match from results list.
> 
> Magnus, does your patch in bug 1043310 fix this?

It should make all cases where you blur (leave) the autocomplete widget to use the thing we found and nothing else. AND, if the text in the autocomplete widget is already one of the search results, we make sure not to change the text. So I'd say yes.
Flags: needinfo?(mkmelin+mozilla)
Same result, repeatable:

Type a partial recipient name
Mouse click on one option
Selected address shows in recipient field
Press "Enter"
Address in recipient field reverts to first address in drop-down list

Thunderbird 31.3.0, Windows 7 64-bit.
Duplicate of this bug: 1116997
Same exact behavior.  Able to work-around by left-clicking on a different object or field to shift the focus to the body of the message.

Thunderbird 31.3.0, Windows 7 64-bit.
Confirm this.
Present in Thunderbird 31.3.0, Windows 7 64-bit, Windows 10 Preview.
Not present in Thunderbird 24.2.x
Duping to bug 1107844 which was the same core issue.
Status: NEW → RESOLVED
Closed: 5 years ago
No longer depends on: 1107844
Resolution: --- → DUPLICATE
Duplicate of bug: 1107844
Same issue was reopened in bug 1123532.
You need to log in before you can comment on or make changes to this bug.