(In reply to Alessandro Castellani (:aleca) from comment #6) > I'm personally not totally against removing the "autocomplete-on-comma" feature as I personally don't use it, but I see how it can be useful to users, but also how it requires a bit of a learning curve. All but undiscoverable, so users may never even try. Has anyone ever seen autocomplete-on-comma, anywhere? Firefox location bar does not even allow Tab for autocompletion. > Once the autocomplete kicks in, typing comma to start typing another address is a bit more natural and keeps the flow going then hitting Enter or Tab. > Having addresses saved as "FirstName, LastName ..." seems a bit of an edge case, quiet unusual, and IMHO wrong as we should discourage using these special characters for saved entries. Based on what data? Imho, "Last, First" is quite far from being an edge case... - Dedicated view mode "Last, First" in TB's address book, and fully supported in current TB (composition, address book) - Widespread use case for business, schools, authorities, you name it. Anecdotal evidence: I actually have a bunch of messages from our local administration right in front of me, the person works in section 12 of the local administration of OurCity, using the following address pattern: `Miller, 12, OurCity <l.miller@ourcity.example>` - Default order for many other languages/cultures (although there's a tendency towards the European norm for purposes of communication). In view of the above, I doubt that comma in display name qualifies as a "special character" in users' perception. The above example from local authorities also shows that there are many more use cases than just "Last, First" (note the name of town appended with comma above). > If the user types "Johnson, ", and more than 1 autocomplete gets suggested, he should select the preferred address from the dropdown instead of typing the entire name + email + special characters. Seriously, who does that? - Hmmm, how do I select a *new* address from autocomplete dropdown? - If I can't select it because it doesn't exist, how do I type it into recipient input with this bug? - How do I even autocomplete an existing address |Last, First <foo@bar.com>| from my AB which may have several matching addresses like the following? - John Paul Smith <john@foo.bar> - John, Elton <elton@foo.bar> Typing "John" autocompletes inline to "John Paul Smith", typing "John," prematurely confirms that (this bug), so how do I get the other one with comma from my address book? > As I said, I don't have a strong opinion on this feature, but I think having it is better than not. Well, I'd think having this "feature" is a no-go as it renders entering new valid recipient addresses *and* retrieving existing valid recipients via autocomplete disfunctional...
Bug 1609894 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alessandro Castellani (:aleca) from comment #6) > I'm personally not totally against removing the "autocomplete-on-comma" feature as I personally don't use it, but I see how it can be useful to users, but also how it requires a bit of a learning curve. All but undiscoverable, so users may never even try. Has anyone ever seen autocomplete-on-comma, anywhere? Firefox location bar does not even allow Tab for autocompletion. > Once the autocomplete kicks in, typing comma to start typing another address is a bit more natural and keeps the flow going then hitting Enter or Tab. > Having addresses saved as "FirstName, LastName ..." seems a bit of an edge case, quiet unusual, and IMHO wrong as we should discourage using these special characters for saved entries. Based on what data? Imho, "Last, First" is quite far from being an edge case... - Dedicated view mode "Last, First" in TB's address book, and fully supported in current TB (composition, address book) - Widespread use case for business, schools, authorities, you name it. Anecdotal evidence: I actually have a bunch of messages from our local administration right in front of me, the person works in section 12 of the local administration of OurCity, using the following address pattern: `Miller, 12, OurCity <l.miller@ourcity.example>` - Default order for many other languages/cultures (although there's a tendency towards the European norm for purposes of communication). In view of the above, I doubt that comma in display name qualifies as a "special character" in users' perception. The above example from local authorities also shows that there are many more use cases than just "Last, First" (note the name of town appended with comma above). > If the user types "Johnson, ", and more than 1 autocomplete gets suggested, he should select the preferred address from the dropdown instead of typing the entire name + email + special characters. Seriously, who does that? - Hmmm, how do I select a *new* address from autocomplete dropdown? - If I can't select it because it doesn't exist, how do I type it into recipient input with this bug? - How do I even autocomplete an existing address |Last, First <foo@bar.com>| from my AB which may have several matching addresses like the following? - John Paul Smith <john@foo.bar> - John, Elton <elton@foo.bar> Typing "John" autocompletes inline to "John Paul Smith", typing "John," prematurely confirms that (this bug), so how do I get the other one with comma from my address book? > As I said, I don't have a strong opinion on this feature, but I think having it is better than not. Well, I'd think having this "feature" is a no-go as it can render the following user actions *disfunctional* (wrt comma in display name): - entering new valid recipient addresses - retrieving existing valid recipients via autocomplete
(In reply to Alessandro Castellani (:aleca) from comment #6) > I'm personally not totally against removing the "autocomplete-on-comma" feature as I personally don't use it, but I see how it can be useful to users, but also how it requires a bit of a learning curve. All but undiscoverable, so users may never even try. Has anyone ever seen autocomplete-on-comma, anywhere? Firefox location bar does not even allow Tab for autocompletion. > Once the autocomplete kicks in, typing comma to start typing another address is a bit more natural and keeps the flow going then hitting Enter or Tab. > Having addresses saved as "FirstName, LastName ..." seems a bit of an edge case, quiet unusual, and IMHO wrong as we should discourage using these special characters for saved entries. Based on what data? Imho, "Last, First" is quite far from being an edge case... - Dedicated view mode "Last, First" in TB's address book, and fully supported in current TB (composition, address book) - Widespread use case for business, schools, authorities, you name it. Anecdotal evidence: I actually have a bunch of messages from our local administration right in front of me, the person works in section 12 of the local administration of our city, using the following address pattern: `Miller, 12, OurCity <l.miller@ourcity.example>` - Default order for many other languages/cultures (although there's a tendency towards the European norm for purposes of communication). In view of the above, I doubt that comma in display name qualifies as a "special character" in users' perception. The above example from local authorities also shows that there are many more use cases than just "Last, First" (note the name of town appended with comma above). > If the user types "Johnson, ", and more than 1 autocomplete gets suggested, he should select the preferred address from the dropdown instead of typing the entire name + email + special characters. Seriously, who does that? - Hmmm, how do I select a *new* address from autocomplete dropdown? - If I can't select it because it doesn't exist, how do I type it into recipient input with this bug? - How do I even autocomplete an existing address |Last, First <foo@bar.com>| from my AB which may have several matching addresses like the following? - John Paul Smith <john@foo.bar> - John, Elton <elton@foo.bar> Typing "John" autocompletes inline to "John Paul Smith", typing "John," prematurely confirms that (this bug), so how do I get the other one with comma from my address book? > As I said, I don't have a strong opinion on this feature, but I think having it is better than not. Well, I'd think having this "feature" is a no-go as it can render the following user actions *disfunctional* (wrt comma in display name): - entering new valid recipient addresses - retrieving existing valid recipients via autocomplete
(In reply to Alessandro Castellani (:aleca) from comment #6) > I'm personally not totally against removing the "autocomplete-on-comma" feature as I personally don't use it, but I see how it can be useful to users, but also how it requires a bit of a learning curve. All but undiscoverable, so users may never even try. Has anyone ever seen autocomplete-on-comma, anywhere? Firefox location bar does not even allow Tab for autocompletion. > Once the autocomplete kicks in, typing comma to start typing another address is a bit more natural and keeps the flow going then hitting Enter or Tab. > Having addresses saved as "FirstName, LastName ..." seems a bit of an edge case, quiet unusual, and IMHO wrong as we should discourage using these special characters for saved entries. Based on what data? Imho, "Last, First" is quite far from being an edge case... - Dedicated view mode "Last, First" in TB's address book, and fully supported in current TB (composition, address book) - Widespread use case for business, schools, authorities, you name it. Anecdotal evidence: I actually have a bunch of messages from our local administration right in front of me, the person works in section 12 of the local administration of our city, using the following address pattern: `Miller, 12, OurCity <l.miller@ourcity.example>` - Default order for many other languages/cultures (although there's a tendency towards the "Western" norm for purposes of communication). In view of the above, I doubt that comma in display name qualifies as a "special character" in users' perception. The above example from local authorities also shows that there are many more use cases than just "Last, First" (note the name of town appended with comma above). > If the user types "Johnson, ", and more than 1 autocomplete gets suggested, he should select the preferred address from the dropdown instead of typing the entire name + email + special characters. Seriously, who does that? - Hmmm, how do I select a *new* address from autocomplete dropdown? - If I can't select it because it doesn't exist, how do I type it into recipient input with this bug? - How do I even autocomplete an existing address |Last, First <foo@bar.com>| from my AB which may have several matching addresses like the following? - John Paul Smith <john@foo.bar> - John, Elton <elton@foo.bar> Typing "John" autocompletes inline to "John Paul Smith", typing "John," prematurely confirms that (this bug), so how do I get the other one with comma from my address book? > As I said, I don't have a strong opinion on this feature, but I think having it is better than not. Well, I'd think having this "feature" is a no-go as it can render the following user actions *disfunctional* (wrt comma in display name): - entering new valid recipient addresses - retrieving existing valid recipients via autocomplete