Good points, P F. Xref Bug 1674054. The tricky part is that we also autocomplete on blur (which I have doubts about, see my Bug 1674054 Comment 6), so just enabling the send button for non-pillified addresses is also tricky. As long as we autocomplete on blur, I think we must disable send button as long as there's any non-pillified address.
Bug 1679848 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Good points, P F. Xref Bug 1674054. The tricky part is that we also autocomplete on blur (which I have doubts about, see my Bug 1674054 Comment 6), so just enabling the send button for non-pillified addresses is also tricky, because we'd then autocomplete *after* you click the send button, with potentially unwanted results (e.g when you have typed a@b.com and have a@b.com.au in your AB). As long as we autocomplete on blur, I think we must disable send button as long as there's any non-pillified address. Which, as this bug correctly points out, is also odd. Workaround: just press tab or click anywhere else in the message to pillify on blur, then send.
Good points, P. F. (reporter). Xref Bug 1674054. The tricky part is that we also autocomplete on blur (which I have doubts about, see my Bug 1674054 Comment 6), so just enabling the send button for non-pillified addresses is also tricky, because we'd then autocomplete *after* you click the send button, with potentially unwanted results (e.g when you have typed a@b.com and have a@b.com.au in your AB). As long as we autocomplete on blur, I think we must disable send button as long as there's any non-pillified address. Which, as this bug correctly points out, is also odd. Workaround: just press tab or click anywhere else in the message to pillify on blur, then send.