enhancement UI inconsistencies with translate "buttons"

[Gareth Cantrell]

I have noticed there are a number of inconsistencies with how the "Translate" button is displayed within a request.

• In the Details panel, it is shown as standard text at the bottom right, with no indication that it is clickable.
• In the Questions panel, it is shown as a blue button with a language icon on the top right.
• In the Timeline, it is shown as smaller standard text with a globe icon to the right of action bar, which attains a light grey background when you hover over it.

 

 

In addition, the displayed translations and ability to remove them are also not consistent:

• In the Details panel, each translated field shows the translated text in a yellow highlight below the original text, within the field and the Translate "button" changes to "Cancel Translate"
• In the Questions panel, all the questions are translated and displayed in a block with a yellow highlight below the original questions. The translate button is disabled so you cannot remove the translated block.
• In the Timeline, the translated content is shown in a block below the original content with no highlighting and the attribution text/link is left-aligned with the translation. The Translate "button" changes to blue and clicking it again removes the translated text.

All of this is happening in a single screen and the experience feels quite disconnected.

[Gareth Cantrell]

Also, I was wondering if the "Translated by Google" link is required or if that can be removed, particularly when we supply our own Google Translate API key.

EDIT: I'm referring to the link that takes you to translate.google.com, not the attribution text.

[David Hall]

Hi @Gareth Cantrell

As is clear from the differences you've highlighted there are several separate components in use here.  I've asked the relevant development team to review to see if we can consolidate around one style then we'll update the app as needed.  To my knowledge the link is required but I'll also ask the dev team to confirm that.

Kind regards,

Dave.

[Gareth Cantrell]

@David Hall I appreciate that there are different components in use, however, as they are all presented in the same view, there should be consistency in their rendering in order to provide a better user experience as they offer the exact same functionality.

As for the attribution link, I re-read the full attribution requirements, and the link is mandatory, so all good there.