Page is still translated with no indication or option to revert after leaving and coming back |
|||||
Issue descriptionChrome Version: 59.0.3054.0 dev Device Type: iPhone 7 Steps to reproduce: (1) Go to a page with a different language from device language. (2) When Chrome offers to translate, tap TRANSLATE (3) Tap DONE (4) Go to another page (5) Go back to translated page Expected result: Should be some indication that the page has been translated with an option to show the original page. Actual result: The page is still translated, but there's no indication of the translation or option to show the original.
,
Apr 3 2017
,
Apr 5 2017
My quick thought is to either force a reload in these scenarios or to show the infobar upon returning that says the page has been translated and gives the option to show the original. Not sure about the feasibility of either. +Bruno who might know if there is assist thinking on this scenario already.
,
Apr 5 2017
Forcing a reload is not a great user experience in my opinion. If a user translated content, then left the tab and came back, they probably want to see the page as they left it. The new mobile UI that we're working on now avoids this issue by keeping the Translate infobar in place and showing which language the page is in (whether original or translated target) unless the user dismisses it (go/easier-translate). I think if the user dismisses the bar we should honor that even in the case of leaving a tab and coming back to it.
,
Apr 11 2017
I agree with Yana's comments. Additionally, my mental model is that pages in the history stack are not necessarily representations of their original state, but rather where the user left off.
,
Apr 11 2017
Marking as won't fix. Please reach out off bug if you vehemently disagree :)
,
Apr 27 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pinkerton@chromium.org
, Apr 3 2017Components: UI>Browser>Translate
Labels: Type-Feature