Could you check what font is being used? Perhaps they renamed one of the fonts again?

Any hint how to check that for sure?

OK, developer tools in chrome for this page says the rendered font is Arial Narrow for the body text of the comment (CSS selector pre.issuetext)

The Arial Narrow seem to be weird choice to render the CSS arial or sans-serif font. Is this mapping under control of the user?

Other thing I observed is that Chrome cannot display Times New Roman font correctly - this is default font in settings, but the example is displayed as some sans-serif font, not serif Times-like.

The ideone.com editor behaves weidrly, as the font in the editor is narrower than the measured text length in the line, so the cursor is positioned incorrectly.

Thank you for providing more feedback. Adding requester "eae@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Interesting, that seems to indicate that Arial isn't available or fails to load.

Michael, from a command prompt could you run the following command, and attach the reg_fonts.txt file?
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts" >reg_fonts.txt

I don't see anything wrong with Arial or Verdana (which seem to be problematic as well).

Interesting fact is that if I switch standard fonts from Times New Roman to Georgia Pro and Arial to Arial Nova, several pages (including this one) displays a little bit better.

It's like Chromium would loose ability to render Times New Roman, Arial and couple other fonts, once new fonts are rendered properly.

Deleted: reg_fonts.txt 36.1 KB

reg_fonts.txt 36.1 KB View Download

If you navigate to C:\Windows\Fonts do you see Arial in the list? If you doubleclick Arial, then doublclick "Arial Regular", does that look normal or is it also condensed?

Yes, but I'm using the Polish language as the main language, so it's "Arial zwykła" for me in that window (screenshot attached). Other Windows application seem to display the font correctly (including Edge browser [which by the way blocks Google]), so other application where I see problems is putty, where their standard font is very small in this version of Windows.

Deleted: Zrzut ekranu (5).png 233 KB

	Zrzut ekranu (5).png 233 KB View Download

I was pointed here from #579678. I'm on Windows 7 and Chrome looks awful when using DirectDraw, so I fell back to GDI until it was removed in Chrome 52.

See screenshots, registry info, attached.

Deleted: chrome-52-win7.png 222 KB

	chrome-52-win7.png 222 KB View Download

#11 is caused by Arial (Regular) being installed outside the system fonts dir. I'm working on a fix for that.

So they are. I've reinstalled the Arial fonts from C:\Windows\Fonts manually from the command prompt, as opening C:\Windows\Fonts in explorer is special.

C:\> cd \windows\Fonts
C:\Windows\Fonts> dir ari*
[...]
C:\Windows\Fonts> start arial.ttf
^ opens the font viewer, click install

repeat for other needed fonts.

Removed #14. We have confirmed that #11 was due to font configuration. If you have information to the contrary, please add it to the appropriate bug (not this one, since this one deals specifically with font configuration). Also this is not the right forum for petitions and advocacy.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/96ce8347f39ce0eebd10de476afb08c0afb406c9

commit 96ce8347f39ce0eebd10de476afb08c0afb406c9
Author: kulshin <kulshin@chromium.org>
Date: Tue Jul 26 00:46:01 2016

Implement support for loading font files from outside system directory

Implement support for loading font files from outside system
directory. When a font file is installed outside the system font
dir, we will now have the browser give the renderer a handle to
the file that it can use to access the font data.

This change will bypass sandbox restrictions that normally
prevents the renderer from opening fonts outside the windows
fonts directory.

BUG= 610466 

Review-Url: https://codereview.chromium.org/2153343002
Cr-Commit-Position: refs/heads/master@{#407658}

[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/browser/renderer_host/dwrite_font_proxy_message_filter_win.cc
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/browser/renderer_host/dwrite_font_proxy_message_filter_win.h
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/browser/renderer_host/dwrite_font_proxy_message_filter_win_unittest.cc
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/child/dwrite_font_proxy/dwrite_font_proxy_win.cc
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/child/dwrite_font_proxy/dwrite_font_proxy_win_unittest.cc
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/common/dwrite_font_proxy_messages.h
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/test/dwrite_font_fake_sender_win.cc
[modify] https://crrev.com/96ce8347f39ce0eebd10de476afb08c0afb406c9/content/test/dwrite_font_fake_sender_win.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8d50cfd5f7036ee15954b328b667e55097b1d313

commit 8d50cfd5f7036ee15954b328b667e55097b1d313
Author: Ilya Kulshin <kulshin@chromium.org>
Date: Mon Aug 01 22:17:40 2016

Implement support for loading font files from outside system directory

Implement support for loading font files from outside system
directory. When a font file is installed outside the system font
dir, we will now have the browser give the renderer a handle to
the file that it can use to access the font data.

This change will bypass sandbox restrictions that normally
prevents the renderer from opening fonts outside the windows
fonts directory.

BUG= 610466 

Review-Url: https://codereview.chromium.org/2153343002
Cr-Commit-Position: refs/heads/master@{#407658}
(cherry picked from commit 96ce8347f39ce0eebd10de476afb08c0afb406c9)

Review URL: https://codereview.chromium.org/2204603002 .

Cr-Commit-Position: refs/branch-heads/2785@{#450}
Cr-Branched-From: 68623971be0cfc492a2cb0427d7f478e7b214c24-refs/heads/master@{#403382}

[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/browser/renderer_host/dwrite_font_proxy_message_filter_win.cc
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/browser/renderer_host/dwrite_font_proxy_message_filter_win.h
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/browser/renderer_host/dwrite_font_proxy_message_filter_win_unittest.cc
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/child/dwrite_font_proxy/dwrite_font_proxy_win.cc
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/child/dwrite_font_proxy/dwrite_font_proxy_win.h
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/child/dwrite_font_proxy/dwrite_font_proxy_win_unittest.cc
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/common/dwrite_font_proxy_messages.h
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/test/dwrite_font_fake_sender_win.cc
[modify] https://crrev.com/8d50cfd5f7036ee15954b328b667e55097b1d313/content/test/dwrite_font_fake_sender_win.h

Tested this issue on Windows-10 using chrome latest Beta M53-53.0.2785.45 by following steps mentioned in the original comment. Observed no rendering issues on sans-serif fonts, Attaching screen-cast for reference.

Note: Due to unavailability of latest chromium builds form the below link unable to verify it on build 407658 from Chrome TE end.
http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?prefix=Win_x64/

Could any one please let us know is there any other source available to download latest chromium builds to verify this issue.

Deleted: SansSerifFont.mp4 710 KB

	SansSerifFont.mp4 710 KB View Download

Good work. They seem all great again. However, have you tested it on Windows 10 Insiders Preview? I'll check these by myself at home.

Marking as verified as per #18

I installed Chromium 54.0.2817.0 on Windows 10 build 14393 and font rendering seems fine now, except the text in the address bar is smaller and less readable (any change in the font used?)

Issue 635932 has been merged into this issue.

Example URL:
Google Inbox

Steps to reproduce the problem:
1. Use more recent (non-DirectWrite) Chrome version
2. 
3. 

What is the expected behavior?
It is now w the DirectWrite feature missing. 

What went wrong?
Chrome updated and didn't include DirectWrite!

Does it occur on multiple sites: Yes

Is it a problem with a plugin? Yes. Depends on the fonts used I assume. 

Did this work before? Yes For years up until this spring. 

Does this work in other browsers? Yes 

Chrome version: 52.0.2743.116  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

I originally had posted to this post months ago (https://bugs.chromium.org/p/chromium/issues/detail?id=618249#) but they closed anymore comments. I just did it again (https://bugs.chromium.org/p/chromium/issues/detail?id=635932#c1) and it was merged into this one. With my first comment from months back, I was able to skirt around this issue by reverting to an older version of Chrome which I will have to now do again. // I've looked at Windows 10 options but to no avail. Other browsers (IE and FF) are rendering pages as they always have. My other laptop seems to be rendering this OK in Chrome. So what was the change in my desktop and Chrome NOT having DirectWrite that wrecks my fonts in Chrome? Please give some solutions to this issue. I need to keep using Chrome.

Deleted: DirectWrite-screencaps=1.png 101 KB

	DirectWrite-screencaps=1.png 101 KB View Download

How is the status Fixed? What do I need to do to get Chrome displaying all pages and texts as it was? Many pages still have the font bolding or condensed as in my screenshot. 

Because you are using version 52.0.2743.116 and need to await (roughly) version 53.0.2785.45 or later (see #18). You can switch to the beta channel if you are impatient enough.

Thanks for the info. I uninstalled all prior Chrome versions and then downloaded Version 53.0.2785.57 beta-m (64-bit) - and that is confirmed in my About settings - but my fonts still look the same. I didn't quite understand in the posts above what other steps I needed to do for it to work. And I'm on Windows 10. Thanks for any more clarity and steps. 

We'll track rizzocreates' bug (#23) in issue 635932.

I've been referred here from forum/#!topic/chrome/-UFETyv9zzw

I have the same narrow font and unexpected italics happening. I'm supposed to attach myself to this issue now. I'm running Version 52.0.2743.116 m on Win 10 and there appears to be no update available.

Please... somebody.... help???