Closed Bug 1689724 Opened 8 months ago Closed 7 months ago

Folder Pane is not enabled after a successful account setup on a clean profile


(Thunderbird :: General, defect, P1)

Thunderbird 86


(thunderbird_esr78 unaffected, thunderbird86 affected)

88 Branch
Tracking Status
thunderbird_esr78 --- unaffected
thunderbird86 --- affected


(Reporter: aleca, Assigned: aleca)




(Keywords: regression)


(1 file, 9 obsolete files)

After concluding a successful first configuration, the email wizard dialog closes but the window remains on the Account Central tab.
The Folder Pane remains collapsed and the UI doesn't updated until the next restart.

This is the error message when completing the "Get new email address" setup:

JavaScript error: chrome://messenger/content/accountUtils.js,
line 422: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)
Version: Trunk → Thunderbird 86

More info:

  • The issue seems to happen only after the creation of a new email.
  • When using an existing email, the UI updates but the selection of the Inbox doesn't trigger the correct loading of the remote folders.
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

I think I found the problems, but I'm not sure if the possible solutions are correct.

UI not loading when an existing account is created on first run
The issue was that the Inbox folder was getting selected before the proper eventListener were set in place, so the selection wasn't triggering any loading of the remove folders or messages.

By removing those setTimeout(..., 0); the startup sequence works as expected.
Are those timeouts necessary?

UI not loading when creating a new email account
The problem is that, after the Account Wizard closes, this condition will always return false ( since we're not passing through the okCallback() method expected from the emailWizard

What should we do here?

Attachment #9200161 - Flags: feedback?(mkmelin+mozilla)
Comment on attachment 9200161 [details] [diff] [review]

Review of attachment 9200161 [details] [diff] [review]:

::: mail/base/content/msgMail3PaneWindow.js
@@ -949,3 @@
>    }
> -
> -  setTimeout(completeStartup, 0);

IIRC this timeout was to allow the main window to come up before the system integration dialog and such. 
I didn't try the patch yet, but as long as things still work properly I'm all for removing setTimeouts.

Ideally showing this dialog would get triggered way later. No real need to do it instantly on startup.

@@ +979,5 @@
> => loadStartFolder(startFolderURI));
>    }
> +  reportAccountTypes();
> +  reportAddressBookTypes();

For these, I think you could put them in a idleDispatchToMainThread instead of setTimeout
Attachment #9200161 - Flags: feedback?(mkmelin+mozilla)
Depends on: 1689079
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

This patch fixes the problem with UI not loading after an existing email account is configured on first run.

I also fixed the issue when a new email is created from the Account Provisioner, but there were some caveats.

I suspect that we might need to update something on that new test site we created to ensure a good response, but I might be wrong and an underlying issue might be present.
Do we know of anyone actually using Ghandi and completing the process?

Since the Account Provisioner overrides the okCallback() of the emailWizard, we don't pass the verifyAccount() condition that would trigger the initialization of the UI. To fix that temporarily, I'm checking if the account provisioner is opened with the args.success attribute, meaning a new email has been created, and if the user has any account currently configured but the folders pane is still collapsed, I trigger the LoadPostAccountWizard() account.

This works only if bug 1689079 is applied.

Attachment #9200161 - Attachment is obsolete: true
Attachment #9200572 - Flags: review?(mkmelin+mozilla)
Comment on attachment 9200572 [details] [diff] [review]

Review of attachment 9200572 [details] [diff] [review]:

::: mail/base/content/msgMail3PaneWindow.js
@@ +902,5 @@
>    }
> +  // Check whether we need to show the default client dialog.
> +  // First, check the shell service.
> +  if (Ci.nsIShellService) {

I don't think this check is a thing. Seems like a leftover from some old code. The nsIShellService interface always exists, but if there's no shell service can be created through the interface.

@@ +933,5 @@
> +        !SearchIntegration.osVersionTooLow &&
> +        !SearchIntegration.osComponentsNotRunning &&
> +        !SearchIntegration.firstRunDone)
> +    ) {
> +      window.openDialog(

For a normal account setup I now get the integration dialog on top of the account setup dialog.
I don't think this used to happen.

It seems all of this could well happen on idle (or even later) as there's no urgency at all to do it directly.

@@ +987,5 @@
> + => {
> +    loadStartFolder(startFolderURI);
> +    reportAccountTypes();
> +    reportAddressBookTypes();
> +  });

No need to do the telemetry reporting on any urgency, so why not the idleDispatchToMainThread?
Attachment #9200572 - Flags: review?(mkmelin+mozilla) → feedback+

I'm stumbling upon a problem where, after a successful account setup, the Inbox folder is selected by the messages and the other folders are not loaded. Clicking on another folder and then selecting again Inbox triggers the loading from the server.

Setting a timeout before letting the code select the Inbox folder solves this problem, but of course that's not good.
That means we probably have a race issue where something is getting configured and we select the Inbox folder too soon.

After trying to trace all the startup calls, I found out that the code stops here on first run:

Any suggestion?

I'm a bit out of my depth here, and it seems that the startup code handling the triggering of the email wizard is shared with seamonkey, so I don't know how much I can change.

I'm starting to think that, since this whole thing with dialogs will be dropped with the account wizard in a tab, maybe we should temporarily ignore this problem, pushing for the new wizard before the next esr.

What do you think?

Flags: needinfo?(mkmelin+mozilla)

If it works for this case to put MsgGetMessagesForAllServers on a timeout, that seems ok. Also add a comment that it's for a clean account so that case doesn't get missed in the future.

Flags: needinfo?(mkmelin+mozilla)
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

All right, this works properly for both Account setup and New Email setup on first run.
I solved the issues of the system integration dialog popping on top of the emailWizard dialog, and the fodler selection happening too early.

Now the UI loads correctly for every scenario, I think.
This whole timeout based process will be dropped entirely after we implement the Account Creation in a Tab, so this is mostly temporary just to not ship glitchy betas when setting up a new account.

Here's a try run to see if I destroyed something:

Attachment #9200572 - Attachment is obsolete: true
Attachment #9202128 - Flags: review?(mkmelin+mozilla)

As I expected, lots of test failures.

Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review
Attachment #9202128 - Attachment is obsolete: true
Attachment #9202128 - Flags: review?(mkmelin+mozilla)
Attachment #9202192 - Flags: review?(mkmelin+mozilla)
Comment on attachment 9202192 [details] [diff] [review]

Review of attachment 9202192 [details] [diff] [review]:

Looks like  comm/mail/test/browser/newmailaccount/browser_newmailaccount.js fails. Maybe comm/mail/test/browser/quick-filter-bar/browser_displayIssues.js as well

::: mail/base/content/msgMail3PaneWindow.js
@@ +887,5 @@
> +  // event liteners, otherwise we risk to select the Inbox folder without
> +  // triggering the loading of the rest of the account on first startup.
> +  setTimeout(selectFirstFolder, 0);
> +
> +  // FIX ME - later we will be able to use onload from the overlay.

I think we can remove this. Have no idea what it's supposed to refer to anymore.

@@ +914,5 @@
> +/**
> + * Check if we need to show the system integration dialog before notifying the
> + * application that the startup process is completed.
> + */
> +function completeStartup() {

we could rename this to be about the system integration for clarity.
Attachment #9202192 - Flags: review?(mkmelin+mozilla)
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

So, apparently the application needs at least a loadStartFolder(null) on startup in order to function, that's why those tests were failing.
I was trying to be smart and interrupt the selection of the start folder in case we didn't pass some conditions, but without that, no proper initial focus/selection is triggered.

Patch updated to keep the same condition structure to select the initial folder.

Another try run:

Attachment #9202192 - Attachment is obsolete: true
Attachment #9202482 - Flags: review?(mkmelin+mozilla)

Comment on attachment 9202482 [details] [diff] [review]

browser_newmailaccount.js is still failing

Attachment #9202482 - Flags: review?(mkmelin+mozilla)

Just to note that the test case added in bug 1693883 had a TODO item to test this bug (at the TODO item, the folder pane should again start showing)

Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

I'm a bit lost with this.
I can't understand why that browser_newmailaccount.js test fails with:
Found an unexpected alert:alert at the end of test run
I'm not able to make the test fail locally, and it passes on macOS in the try-server.

I also run the test with --verify and that had a bunch of different failures, which I fixed, except for a failure that involves the missing Services.logins on a second run.
Removing the Services.logins.removeAllLogins(); method added in bug 1693883 makes the test succeed with --verify but I'm not sure if we should remove it.

I'm not sure where to look and what to try here.

Attachment #9202482 - Attachment is obsolete: true
Attachment #9205025 - Flags: feedback?(mkmelin+mozilla)

I think I found the possible issue.
I just noticed that my Notification panel in Ubuntu showed multiple notifications with Daily failed to connect to server

I suspect this is what that alert:alert reported in the test failure is about, as I think on Linux and Windows those are recognized as system alerts, while on macOS are simply ignored as notifications.

How do we solve this?

I was able to fix the failing tests with the alert:alert issue by implementing a MockAlertService, bu now I'm stumbling up on an old test failure fixed in bug 1663209.

Upon investigating, I found out that the changes in that bug are what caused this regression.
Without the setTimeout() set to 0, the folder is selected too soon after a successful account setup and the initial download of the inbox is not properly triggered.

Regressed by: 1663209
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

Hey Geoff, I'm pinging you to see if you have insights on this.

As I wrote before, removing the setTimeout wrapper for the selectFirstFolder() causes the app to select the first folder without triggering the loading of the messages or the server folders on first run.

With this patch, the startup process after a successful setup completes correctly, but of course it causes an issue in this test that you previously fixed:

I'm a bit stuck with this patch and I'm not sure what to do here as it seems that the FolderPaneSelectionChange() method doesn't do its job if the Inbox folder is selected too soon on a fresh install.

Attachment #9205025 - Attachment is obsolete: true
Attachment #9205025 - Flags: feedback?(mkmelin+mozilla)
Attachment #9205289 - Flags: feedback?(geoff)


setTimeout(selectFirstFolder, 0);

with: => selectFirstFolder());

That seems to do the trick. I've had a fight with setTimeout here before (bug 1663209) but I've never really understood the problem.

I tried that, sorry, I should have wrote that in my previous message.
Using => selectFirstFolder()); doesn't properly trigger the load of the server at the end a new account setup.

Found it! There are two things calling getNewMessages and the back end is getting confused.

Of the two, I'd remove the first because it shouldn't be up to the wizard to fetch new mail.

Comment on attachment 9205289 [details] [diff] [review]

Review of attachment 9205289 [details] [diff] [review]:

I haven't looked at this all that closely, but enough to figure out what you're up to, and it seems okay to me.

::: mail/base/content/msgMail3PaneWindow.js
@@ +836,5 @@
> + * in case a user configures a new email account on first run.
> + *
> + * @param {boolean} isFromProvisioner - True if the method was called from the
> + *   New Account Provisioner. This is used to avoid triggering the system
> + *   integration dialog since the New Account Provinsioner uses a secondary

Provinsioner! :-)
Attachment #9205289 - Flags: feedback?(geoff) → feedback+

(In reply to Geoff Lankow (:darktrojan) from comment #22)

Found it! There are two things calling getNewMessages and the back end is getting confused.

Of the two, I'd remove the first because it shouldn't be up to the wizard to fetch new mail.

Ah! Here's the culprit.

The email wizard one doesn't really do anything as it doesn't actually trigger the loading of new folders and messages.
We need to keep that as it's necessary for 2 scenarios:

  • On first startup when no accounts are configured, the email wizard needs to trigger the fetching after a successful setup because selecting the newly created Inbox folder doesn't load anything without a timeout.
  • If the user already has an account and creates a new one, we won't go through the loadStartFolder.
Attached patch 1689724-account-setup-after.diff (obsolete) — Splinter Review

A tiny fix to properly load folders and messages of newly created accounts.
Tested this by manually creating 3 accounts in a row and everything seems to work like a charm.

Attachment #9206531 - Attachment is obsolete: true
Attachment #9206531 - Flags: review?(mkmelin+mozilla)
Attachment #9206534 - Flags: review?(mkmelin+mozilla)
Comment on attachment 9206534 [details] [diff] [review]

Review of attachment 9206534 [details] [diff] [review]:

::: mail/base/content/msgMail3PaneWindow.js
@@ +875,5 @@
> +    setTimeout(showSystemIntegrationDialog, 0);
> +  }
> +
> +  let safeMode = document.getElementById("helpSafeMode");
> +  let appSafeMode = document.getElementById("appmenu_safeMode");

would move these down into the if, where they are used

@@ +924,5 @@
> +  } catch (ex) {}
> +  let defaultAccount = accountManager.defaultAccount;
> +
> +  // Try loading the search integration module.
> +  // We'll get a null SearchIntegration if we don't have one.

I don't think this is true. We ship SearchIntegration.jsm for all platforms. It doesn't DO anything on linux.
if the module is not there the import will throw.

::: mail/test/browser/newmailaccount/browser_newmailaccount.js
@@ +77,5 @@
>  var kSuggestFromNamePref = "mail.provider.suggestFromName";
>  var kProviderListPref = "mail.provider.providerList";
>  var kDefaultServerPort = 4444;
>  var kDefaultServerRoot = "http://localhost:" + kDefaultServerPort;
> +var kDefaultEngine;

use g prefix for when you're just storing a global variable that is not a constant
Attachment #9206534 - Flags: review?(mkmelin+mozilla) → review+

Thanks for the review.

Attachment #9206534 - Attachment is obsolete: true
Attachment #9206704 - Flags: review+
Target Milestone: --- → 88 Branch

Pushed by
Fix UI not updating after a new account setup. r=mkmelin

Closed: 7 months ago
Resolution: --- → FIXED
Regressions: 1696380
You need to log in before you can comment on or make changes to this bug.