1800877 - Autocomplete popup is not wide enough to display full addresses when editing a recipient pill (worse for short pills)

Status: NEW

(Thunderbird :: Message Compose Window, defect)

Description

[Arthur K. (he/him)]

Attachment: autocomplete-choices-cut-off.png

First observed in 108.0b1:

STR:

1. Compose a new email in the "To" field to an email address you know is in autocomplete (i.e., [e-mail]) and choose it as the recipient by pressing Enter
2. Once the email has been chosen, go back to it using the left arrow key or click on it to highlight it
3. With the email address highlighted, press F2 to edit it
4. The blinking cursor will be at the far right of the email address so begin pressing the Backspace key until it deletes everything up to the @ symbol
5. Start typing the remainder of the email address you had chosen earlier but only add one letter after the @ symbol (i.e., abuse@g)

Expected Results:

1. The width of the autocomplete window displays the domain name and everything after the @ symbol

Actual Results:

1. The width of the autocomplete window is cut off and doesn't show you the full domain name after the @ symbol

Comment 1

[Arthur K. (he/him)]

Error Console is showing me this upon completing STR step 1 and 2:

NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:163
observe resource://gre/modules/LoginManagerChild.jsm:163
handleEnter chrome://global/content/elements/autocomplete-input.js:579
handleKeyDown chrome://global/content/elements/autocomplete-input.js:544
AutocompleteInput chrome://global/content/elements/autocomplete-input.js:39

Comment 2

[Thomas D. (:thomas8)]

Confirming. Thanks Arthur, yes, this is happening, and it's odd.
Maybe not a super-frequent use case - more like an error correction thing, right?

This isn't new to 108. Already seen on 91. Probably on record already somewhere.

Comment 3

[Arthur K. (he/him)]

(In reply to Thomas D. (:thomas8) from comment #2)

Confirming. Thanks Arthur, yes, this is happening, and it's odd.
Maybe not a super-frequent use case - more like an error correction thing, right?

This isn't new to 108. Already seen on 91. Probably on record already somewhere.

Interesting. I've gone all this time and never hit it. I frequently do a secondary auto-correction---a la my STR repro steps---of an autocompleted email and never hit it until 108. I'd be curious if it was around since 91 as I never hit it once from 91 > 107. Would love to see other reports if you find them.

Comment 4

[Arthur K. (he/him)]

I couldn't repro using a clean TB Portable 102.4.2. So then I tried something that felt like it might help manifest the issue. I copied over my abook.sqlite and my history.sqlite from my 108.0b1 profile to my clean instance of 102.4.2 and it now repros there. Eesh.

So I went further to make sure I am not nuts. I deleted the copied over abook.sqlite and history.sqlite with 102.4.2 closed and restarted fresh and I was not able to repro.

So I went further yet! With 102.4.2 having both a clean abook.sqlite and history.sqlite file, I only copied over history.sqlite and left abook.sqlite alone. The issue repros.

Then, with 102.4.2 having both a clean abook.sqlite and history.sqlite file, I only copied over abook.sqlite and left history.sqlite alone. The issue repros.

So it appears to be something with my abook.sqlite and history.sqlite files.