(In reply to comment #86)
> >+ // Error condition
> >+ message.AssignLiteral("String ID ");
> >+ message.AppendInt(aMsgId);
> >+ FEAlert(message, aUrl);
> I assume we only expect to hit this in development so we don't need to know
> which server is reporting the alert?
Correct, in theory l10n development can hit this, though with l10n merge that's less likely. It is just what we did before as a fallback so I kept it.
> >+imapLoginFailedRetryButton=Retry
> No access key? (&Retry iirc)
nsIPrompt::confirmEx doesn't give us an access key option. The only way we could do something about this would be to spin our own prompt dialog. Whilst I can see that happening after the next major version of TB/SM, I'm not sure it is what we want to do now.
(In reply to comment #86) AssignLiteral( "String ID "); AppendInt( aMsgId) ;
> >+ // Error condition
> >+ message.
> >+ message.
> >+ FEAlert(message, aUrl);
> I assume we only expect to hit this in development so we don't need to know
> which server is reporting the alert?
Correct, in theory l10n development can hit this, though with l10n merge that's less likely. It is just what we did before as a fallback so I kept it.
> >+imapLoginFail edRetryButton= Retry
> No access key? (&Retry iirc)
nsIPrompt: :confirmEx doesn't give us an access key option. The only way we could do something about this would be to spin our own prompt dialog. Whilst I can see that happening after the next major version of TB/SM, I'm not sure it is what we want to do now.