Example URL:
https://www.aqua-mail.com/forum/index.php?topic=6641.0

Steps to reproduce the problem:
I'm trying to report an Android WebView rendering issue, and WebView since 7.0 is actually Chrome.

1 - We're an email app for Android called Aqua Mail

2 - Some time in summer 2018 we started receiving user complaints about "overlapping text" in our message view

3 - Our message view is a WebView into which we load a message's content with some custom HTML wrappers and stuff (basically we add div's around the original content and include some CSS rules for things like nice "quoted text" indentation, link color, that kind of thing).

4 - Complaints are of "strangely overlapping text".

Screenshots are available on our forum https://www.aqua-mail.com/forum/index.php?topic=6641

and I'll try to attach some here.

5 - ... which goes away if the user pinch-zooms a little, or adjusts font size (for this our code calls WebSettings#setTextZoom).

6 - Either way (pinch-zoom or font scale adjustment) - we don't make any changes in the already loaded HTML from our side.

7 - The issue began between our app's releases.

8 - So far the only reported devices are Xiaomi and Huawei.

Not all of them though, our QA and Dev teams have a few of these, but are not able to reproduce the issue (even with same exact .eml files sent by users).

9 - We do not "mess with" anything like line-height or any similar CSS properties.

10 - Usually we load the HTML with WebView#loadDatawithUrl, but then changed to send the HTML as a string to JavaScript inside the WebView and have JavaScript parse the string and put into a pre-defined DIV using DOM APIs. Did not help.

Any ideas what could be causing this?

How can we troubleshoot this?

What is the expected behavior?

What went wrong?
Corrupted text display.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 69.0.3497.100  Channel: stable
OS Version: 8.0
Flash Version: 

It really looks like the issue is in Chrome not on our side, and it has to do with some sort of cache or possibly a race condition - since the corrupted rendering goes away if user forces a repaint, and this doesn't cause a change in actual HTML tree.
 

Deleted: Screenshot_20180919-091840.jpg 469 KB

	Screenshot_20180919-091840.jpg 469 KB View Download

Deleted: Screenshot_20180919-091920.jpg 150 KB

	Screenshot_20180919-091920.jpg 150 KB View Download

Deleted: Screenshot_20180919-092017.jpg 164 KB

	Screenshot_20180919-092017.jpg 164 KB View Download