If I reload a translated page, it is shown in the native language with the translation prompt again.

jzw@: Hmm it didn't for me. did you try the exact same page? It might be page dependent.

michaeldo & eugenebut, please help triage this.

Yeah for me it always auto translates the second page without showing any translate UI. If I reload the page it'll be native again and show the initial translate UI.

I investigated slightly and this is what I've found. Language detection is done in two ways:

1. HTML headers. content-lang and lang.
2. CLD (Chrome Language Detector?). This works by looking at a portion of the text in the page.

In an untranslated page these two match and the language can be determined. But if a page is already translated, which happens when you go back to a cached page, the two methods now disagree and the language code is determined to be "und" (undetermined). This would prevent any UI from being presented. If navigating back is a cache miss, then the entire page is loaded again and now both methods match and the UI is presented normally.

Hopefully this helps whoever looks at this from the translate team :)

Hey droger@, it seems you are most familiar with language_detection_util.cc, would you be able to advise on this issue?

A specific case of crbug.gcom/795573

Do you know if this is specific to iOS?

If the analysis in comment #6 is right, then one solution could be to save the translation status of the page (including the original language probably) in the history, and use that when navigating back.

This looks like relatively low priority, and I don't have time to work on this now unfortunately. Marking as available for now.

I believe this is iOS specific. If we can make it so after navigating back to a cached page, it initiates translation with state AFTER_TRANSLATE, then we'd be able to present to the user that the page has been translated.

Bulk assigning iOS-specific Translate bugs to ghendel@ for triage as per our discussion.