Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.6 using chrome version 53.0.2785.101 and canary 55.0.2858.0.

This is non regression as it is observed from M30 old builds.Making it as Untriaged to get more inputs from dev team.

Thanks,

+ftang who might know more about how the Translate Server does this (and why). This does not happen in Chrome - it's translate.google.com that does the actual translation.

Adding an example, the page's header is converted from
<h1>挪威的森林&nbsp;第一章 永遠記得我</h1>

to
<h1><font><font>Norwegian Wood will always remember my first chapter</font></font></h1>

The header translation has no problem. We need to insert <font> tag for reordering and splitting which is not a problem visually. The bug is not because we insert the <font>, but the insertion has a bug cause all the <br> push down to the bottom of the page. The <br> are still there, but in the wrong place and cause the format massed up. I will track this in Google translate internal bug. Thanks for reporting this.

The internal bug number is 31457229 just for googler's to track in case.

The bug is fixed last week with new Translate Element push.