This should block... something. Looks like we might not retry the dictionary download on failure until SpellcheckService spins up again (on restart?) Today, old Options is the only caller of SpellcheckHunspellDictionary::RetryDownloadDictionary.

IIRC we shouldn't auto-retry, because there are bandwidth costs associated with that. 

+yyushinka for spellcheck PM

I wouldn't mark it as blocker unless we have evidence this actually affects a large number of users. 

Re: bandwidth costs. Would we have comparable total bandwidth requirements in the case of no failure as in the case of failure+retry (e.g. if the failure is usually that the download never initiates)? In that case auto-retrying still sounds like the better solution for the user.

Please confirm: right now when the user enables a new spellcheck language, we attempt to download the dictionary. If we fail, we retry on each chrome restart? There used to be a manual retry button but it's gone with MD.

This is not awesome (presumably the user turned on spellcheck and would like to use is now). Agree not a blocker, though would like to add auto-retry. @groby, does exponential backoff address your concerns? or are you thinking we need resumable downloading for this? (how big are dictionaries, anyway?)

@aee: Has this been addressed now as part of  issue 820456 ?

Yes, I'll mark this as a duplicate.

If the dictionary wasn't downloaded, the dictionary download is attempted when chrome starts. If the download fails, the UI shows an error and a retry button in the spellcheck settings to allow the user to retry the download.