New issue
Advanced search Search tips

Issue 896670 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Device Toolbar breaks Font-Rendering

Reported by bkwas...@ymail.com, Oct 18

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36

Steps to reproduce the problem:
1. Use a non standard font (eg. from google fonts) 
2. Open Developer Tools and toggle the Device Toolbar
3. Reload Page
4. The Font-Rendering is now broken
5. Close Devloper Tools (dont toggle the Device Toolbar)

The Font-Rendering is now broken (till you toggle the device toolbar off).

What is the expected behavior?
Default Font-Rendering, like it is without opening the Device Toolbar.

What went wrong?
Font-Rendering keeps broken 

Did this work before? N/A 

Chrome version: 70.0.3538.67  Channel: stable
OS Version: 10.0
Flash Version: 

Its hard to see in the screenshots. 
You can better test the html, which i attached. There you can better see that the font is not rendered correctly.
 
chrome_correct.png
66.8 KB View Download
chrome_broken.png
53.9 KB View Download
chrome_font_bug.html
2.4 KB View Download
Owner: l...@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: skobes@google.com
Thanks for the report.  I'm unable to reproduce this issue on Linux, Mac, M69, M72.

On the surface, this issue looks similar to crbug.com/797352 where font sizes were not correctly applied 'sometimes' when Device Mode is enabled.  In the other report, it suggested adding width=device-width in the viewport descriptor:
  <meta name="viewport" content="width=device-width">

skobes@, maybe you have ideas why this might occur?
From the screenshots, this looks like an antialiasing issue, not a font size issue.  Maybe mobile emulation applies different antialiasing settings?
<meta name="viewport" content="width=device-width"> didnt fixed it for me.
It could be a antialiasing  issue (is there a way to check it?).
But if mobile antialiasing is different to the default antialiasing, it should switch back when leaving the developer tools (even when i dont close the device toolbar).

I mean, the antialiasing is the only difference I see between chrome_correct.png and chrome_broken.png, so I'm assuming that's what you're referring to when you say the "Font-Rendering is now broken".  But I don't know the root cause of the bug.

@luoe have you tried to repro on Windows?
Yes, I'm able to reproduce on a Win10 computer.  Having antialiasing change when entering mobile emulation is expected, but when exiting Device Mode, I'd expect that the antialiasing returns to "normal/desktop".

If we can get the normal aliasing to be equivalent to the [emulate mobile + unemulate mobile] case, that'd be less surprising to me.  I'll take a look at the emulator code.

Thanks!

Sign in to add a comment