(In reply to Deven Corzine from comment #43)
> This worked in Thunderbird 2, which means it's a regression bug, not an
Fwiw, notwithstanding the annoyingness of this bug, it is NOT a regression.
I just tested this on TB version 2.0.0.24 (20100228), and nicks do NOT get absolute precedence in composition's recipient autocomplete (but it's easy to get fooled into thinking they do).
(In reply to Deven Corzine from comment #43)
> This worked in Thunderbird 2, which means it's a regression bug, not an
Fwiw, notwithstanding the annoyingness of this bug, it is NOT a regression.
I just tested this on TB version 2.0.0.24 (20100228), and nicks do NOT get absolute precedence in composition's recipient autocomplete (but it's easy to get fooled into thinking they do).
I tested with this scenario (basically):
Card1:
firstname: n1n
email: <email address hidden>
nick: n2n
Card2:
firstname: foo
email: <email address hidden>
nick: n1n
STR
1 compose new msg
2 in TO recipient field, type "n1n"
Actual Result:
- card 1 is at top of autocomplete list
- ...
Expected Result:
- card 2 having fullstring match of nick should be at top of autocomplete list