Issue metadata
Sign in to add a comment
|
Translate bar is not accesible after closing it
Reported by
mic...@peterson.com.ar,
Jul 16 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Two options, for two different related bugs: 1. Enter a web that will prompt for translate (choose translate from there or from the context menu by right clicking on the page) 2. Close the translation bar 3. Try to find a way to go back to the original language What is the expected behavior? To find, like in the Windows version, a button at the end of the URL bar where it's possible to revert back to the original language. What went wrong? There is no way to returning to the original language since the translate feature is no longer accesible. Did this work before? Yes don't know Chrome version: 59.0.3071.115 Channel: stable OS Version: OS X 10.12.5 Flash Version:
,
Jul 16 2017
As you can see, in windows the translate facility is always available from the translate icon in the URL bar, whereas in OSX is not available aynmore once you close it.
,
Jul 16 2017
Thank you for providing more feedback. Adding requester "mehmet@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 16 2017
Re-uploaded the OSX version in mp4
,
Jul 16 2017
Hello michel@: Thanks for your feedback. On Windows, you are seeing the New Translate UX, which can be activated via chrome://flags/#enable-translate-new-ux After I have activated it on macOS, I am also seeing the icon in the Omnibox instead of the Translation Bar. From my point of view, we can close this issue, right?
,
Jul 18 2017
I guess if it's going to be activated by default in the future, then yes. However, I would like to note that how it works right now, it's a big problem not being able to translate back to the original message. And I don't remember having this problem in the past. Thanks a lot!
,
Jul 21 2017
We're not shipping that new UI so fine to close as won't fix. Jon can we make sure none of the 2016Q2UI's (whether the Mac or the Views one) are running in an experiment anymore?
,
Jul 25 2017
As per comment #7, closing this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Jul 16 2017Labels: Needs-Feedback