Google Sans r is rendered higher when followed by t |
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3430.0 Safari/537.36 Steps to reproduce the problem: 1. Use the new GMail. 2. Open an e-mail with a title that has a word that features the "rt" letter sequence (webrtc, part...). What is the expected behavior? "rt" renders normally - the r does not start at the same position as the t. What went wrong? "rt" renders badly - the r starts at the same position as the t. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 68.0.3430.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I tried Internet Explorer 11 and it renders fine. The screenshot was taken with ClearType disabled, but it happens even when it is enabled.
,
May 15 2018
,
May 18 2018
Likely a hinting issue, not sure there is much we can do about it. You seen this before drott?
,
May 19 2018
#3 - Internet Explorer renders this fine, so how can you not do anything about it? I assume they did not single out that specific font (it is much newer than Internet Explorer and they do not fix non-high-severity issues anymore). ;)
,
May 21 2018
> The screenshot was taken with ClearType disabled, but it happens even when it is enabled. Would you have a screenshot illustrating the problem without forcing Chrome into bilevel rendering? How was this screenshot acquired, just by using ClearType tuner, or alternative methods of forcing this rendering mode?
,
May 21 2018
#5 - ClearType was disabled and smooth font edges were disabled using the standard Windows 10 methods (that old System Performance tab and the ClearType tuner, yes). The attached is a screenshot from Windows 7, with font smoothing and ClearType enabled. Same issue, just a bit prettier font.
,
May 26 2018
Also, Roboto in the thread list adds some space between RT and C (ClearType/font smoothing disabled). Subject - "Issue 846976 in chromium: RTCDataChannelInit maxRetransmits = null causes channel to act as if it were unreliable." If I add/change letters before "TC", it makes it a bit better (the gap is narrower).
,
Jun 4 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by phistuck@chromium.org
, May 15 2018