Bugzilla

(Re-filing the confusing bug 1907443)

In account setup, with Exchange AutoDiscover, we show a username field, but only when necessary, that is, when the server returns a HTTP 401. That old code is racy. Only by coincidence, in TB 128, that race does not actually happen, because the new OAuth2 prompt during AutoDiscover waits for user input and blocked the racing function.

We submit a fix that makes this code cleaner, more reliable, not racy anymore, and also more readable.

(Re-filing the confusing bug 1907443)

In account setup, with Exchange AutoDiscover, we show a username field, but only when necessary, that is, when the server returns a HTTP 401. That old code is racy. Only by coincidence, in TB 128, that race does not actually happen, because the new OAuth2 prompt during AutoDiscover waits for user input and blocked the racing function.

This is a fix that makes this code cleaner, more reliable, not racy anymore, and also more readable.

(Re-filing the confusing bug 1907443)

In account setup, with Exchange AutoDiscover, we show a username field, but only when necessary, that is, when the server returns a HTTP 401.

That old code is racy. Only by coincidence, in TB 128, that race does not actually happen, because the new OAuth2 prompt during AutoDiscover waits for user input and blocked the racing function.

This is a fix that makes this code cleaner, more reliable, not racy anymore, and also more readable.

(Re-filing the confusing bug 1907443)

In account setup, with Exchange AutoDiscover, we show a username field, but only when necessary, that is, when the server returns a HTTP 401.

That old code is racy. Only by coincidence, in TB 128, that race does not actually happen, because the new OAuth2 prompt during AutoDiscover waits for user input and blocked the racing function.

This is a fix that makes this code cleaner, more reliable, and not racy anymore.