Issue metadata
Sign in to add a comment
|
[Component Request] UI>Browser>Language>Translate>Element |
||||||||||||||||||||||
Issue description1] Component Name: Element 2] Parent Component (e.g. Blink, UI>Browser, etc...): UI>Browser>Language>Translate 3] Description of Component: Issues caused by the translate element, including incorrect layout, visual defects, non-functioning UI components, etc. 4] Admin/ Owner: napper@chromium.org 5] Our triage document is here: https://docs.google.com/document/d/1fgqNfmN5sZLeV1uj8tph0Jy15jts2gg3UpypCEWxYr4
,
Jul 12 2017
Yes, good question. I am trying to differentiate between issues that cause the translation to fail (e.g., network errors, CSP blocking, broken API keys, etc.) and the large number of much more minor formatting or layout issues that are caused by translate replacing text in one language with another. Element probably isn't a good name. Maybe Translate>Content? Translate>Results? Translate>Quality?
,
Jul 12 2017
My two cents: Translate>Translated Content or Translate>Translation Quality make the most sense to me.
,
Jul 12 2017
Either of those sound fine to me. How about: Translate > Translated Content
,
Jul 20 2017
Friendly ping. Is there any more info required here?
,
Jul 21 2017
This seems like something that should be tracked w/ a hotlist, rather than creating a new categorization that won't be readily understood.
,
Jul 23 2017
Understood. We will use a hotlist instead. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lafo...@chromium.org
, Jul 12 2017