1907445 - Cardbook does not autocomplete with Thunderbird 128 ESR.

Status: RESOLVED INVALID

(Thunderbird :: Message Compose Window, defect)

Description

[Sam]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Edg/124.0.0.0

Steps to reproduce:

Opened a new message and typed part of a name.

Actual results:

CardBook did not autocomplete the recipient address and give me choices for the recipient.

Expected results:

Cardbook should autocomplete as it did with Thunderbird 115.

Comment 1

[Ramona Gavrilescu]

Hello,

I have tried to reproduce you issue with 128.0esr (20240710185639) using Windows 11 and Windows 10 but did not manage to encounter the behaviour.

Can you give us any other relevant information that would help us reproduce this issue? (using IMAP/POP3 account?, single or multiple accounts, etc). Does this only happen for you on the latest 128.0esr?

If you can still reproduce this issue with the same repro steps, it would very helpful if you could indicate the affected versions on which you are able to reproduce it-if any(besides the 128.0esr on which you have encountered it) and if time allows, help us with a regression range for this issue.
I will provide the steps necessary.

You have to determine a build that reproduces the issue. In your case it seems Thunderbird v128.0esr right?

Then you should find one that does NOT reproduce it.

Detailed steps:

a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-06-21 to have a better chance finding one that does not reproduce the issue) from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Comment 2

[Francesco]

CardBook is a Thunderbird add-on. The problem should be referred to its author. IMHO, no need to find any regression here.

Comment 3

[Wayne Mery (:wsmwk)]

Cardbook claims to be compatible with 128, and before this bug report there no reported open issues for version 128 https://gitlab.com/CardBook/CardBook/-/issues

However, I do see an approval review pending for a newer version cardbook.

Comment 4

[Sam]

Many thanks. My bug report should probably be closed since I should have reported it to the add-on author.

Comment 5

[John Bieling (:TbSync)]

The author released a new version to adress this issue.