Bugzilla

The problem of accepting the first (random) autocomplete suggestion prematurely upon comma will be even more exposed for users with AB setting "View > Show Name As > Last, First": In spite of contacts side bar showing all contacts as `Last, First`, entering any known "Lastname," into address input will trigger premature pill creation from a random first autocomplete match (see screenshot: typing the comma now will autocomplete first result). But we explicitly allow searching for last names followed by comma since bug 1630330 as an intuitive and efficient way of narrowing down your AB search / autocompletion, especially for large entities/enterprise (while the difference in matches between contacts side bar and autocomplete looks like another bug).

The problem of accepting the first (random) autocomplete suggestion prematurely upon comma will be even more exposed for users with AB setting "View > Show Name As > Last, First": In spite of contacts side bar showing all contacts as `Last, First`, entering any known "Lastname," into address input will trigger premature pill creation from a random first autocomplete match (see screenshot: typing the comma now will autocomplete first result). But we explicitly allow searching for last names followed by comma since bug 1630330 as an intuitive and efficient way of narrowing down your AB search / autocompletion, especially for large entities/enterprise.

Note: the difference in matches between contacts side bar and autocomplete is bug 1644026, and LDAP autocomplete was off.