Bugzilla

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.

- With Andrei, we created https://github.com/thundernest/static-test, so we can update the pref to point to `https://static-test.thunderbird.net//providerList` to simulate a new email creation process locally.
- When reaching this part: https://searchfox.org/comm-central/rev/4eb14a03690b8d6bbe53853a33b6e09d330a05ea/mail/components/newmailaccount/content/uriListener.js#189-196, the listener fails returning this error: `client config xml = {"parsererror":{"sourcetext":"\u001f\b","$sourcet`
- If I manually write the config.xml file like we do in the tests, the whole process completes successfully.

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.

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.

- With Andrei, we created https://github.com/thundernest/static-test, so we can update the pref to point to `https://static-test.thunderbird.net/providerList` to simulate a new email creation process locally.
- When reaching this part: https://searchfox.org/comm-central/rev/4eb14a03690b8d6bbe53853a33b6e09d330a05ea/mail/components/newmailaccount/content/uriListener.js#189-196, the listener fails returning this error: `client config xml = {"parsererror":{"sourcetext":"\u001f\b","$sourcet`
- If I manually write the config.xml file like we do in the tests, the whole process completes successfully.

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.