Oops, I ment it works in Chrome 48.x and broken in 49.x+

Google Chrome	49.0.2623.108 (Official Build) (64-bit)
Revision	ea59fe695d0d74c18c908438eaf4f53cb0f87ed8-refs/branch-heads/2623@{#652}
OS	Linux 
Blink	537.36 (@ea59fe695d0d74c18c908438eaf4f53cb0f87ed8)
JavaScript	V8 4.9.385.33
Flash	21.0.0.197
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.108 Safari/537.36

Windows 7 and Windows 10:
  Chrome 49 - renders all 2000x, 2001x, 2008x, and 2009x.
  Chrome 50 - renders all 2000x, 2001x, 2008x, and 2009x.
  Chrome 51 - renders all glyphs.

Linux:
  Chrome 49 - renders a handful, < 10%
  Chrome 51 - renders a handful, < 10% (same as above)

Mac:
  Chrome 49 - renders ~15% of the glyphs
  Chrome 51 - renders ~15% of the glyphs (same as above)

On linux the poor support is likely due to my lack of fonts.

My observations does not appear to match yours. On Linux and Mac the rendering is identical between 49, 50 and 51. On Windows it's gotten better in 51.

What OS are you on and do you have a font with coverage for all these glyphs?

Chrome 49 does not render 2000x, 2001x, 2008x, and 2009x for me either on MacOS X 10.11.4 or Windows 7 (haven't tested Linux). All other browsers (IE11 and FF45 on Win7, Safari and FF45 on Mac) and programs on those two platforms render the glyphs just fine. Interestingly, Chrome 49 *does* display the glyphs in question when they are part of the text in the URL in the location bar.

Please note that the characters missing are exactly those which have lower 16 bits of their Unicode codes equal to C0/C1 control characters (U+0000–001F, U+0080–009F), space (U+0020), no-break space (U+00A0), and soft-hyphen (U+00AD).
The same thing also happens at the start of U+10000 range (Linear B syllabary and ideograms blocks). It's not related to availability of fonts.

Sounds a bit like  issue 595960  (although eae's results indicate differently) - any chance you could try the a recent dev channel build and verify?

The problem appears in beta, but I don't see it anymore in 51.0.2693.2 (Official Build) dev (64-bit) 255cb9d4b581ae3eb9a5b582175bc18c7997a741-refs/branch-heads/2693@{#2}.

Seems like it is now fixed.


Google Inc.
Copyright 2016 Google Inc. All rights reserved.
Google Chrome	51.0.2693.2 (Official Build) dev (64-bit)
Revision	255cb9d4b581ae3eb9a5b582175bc18c7997a741-refs/branch-heads/2693@{#2}
OS	Linux 
Blink	537.36 (@255cb9d4b581ae3eb9a5b582175bc18c7997a741)
JavaScript	V8 5.1.216
Flash	21.0.0.204
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2693.2 Safari/537.36
Command Line	/usr/bin/google-chrome-unstable --user-data-dir=/home/dak/.config/google-chrome-unstable --window-depth=24 --flag-switches-begin --flag-switches-end
Executable Path	/opt/google/chrome-unstable/google-chrome-unstable
Profile Path	/home/dak/.config/google-chrome-unstable/Default
Variations	853359fa-f7de5af1
16e0dd70-3f4a17df
da89714-4ad60575
e950616e-ca7d8d80
7c1bc906-e919d5bc
cf5ed6e1-3f4a17df
f049a919-3f4a17df
775ebbd7-3f4a17df
31362330-ca7d8d80
f15c1c09-ca7d8d80
dd4da2fc-3f4a17df
fd02e767-ca7d8d80
9e5c75f1-69b20877
2c3080ba-3f4a17df
64cbdfc2-ca7d8d80
f79cb77b-3f4a17df
10693526-23977274
4ea303a6-a3887510
d5b671a5-3f4a17df
9736de91-3f4a17df
dbffab5d-ca7d8d80
30e679f-ca7d8d80
ad6d27cc-c6d02f41
ca314179-ca7d8d80
69bf80fa-3f4a17df
c8b9b12d-ca7d8d80
a35118-3f4a17df
867c4c68-3d47f4f4
5e3f6590-ca7d8d80
3ac60855-486e2a9c
f296190c-9fa1c5bd
4442aae2-6e597ede
ed1d377-e1cc0f14
75f0f0a0-6bdfffe7
e2b18481-3a9ae350
e7e71889-e1cc0f14
b39ea213-d1372334
6ab14220-3d47f4f4

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://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Awesome, thank you for re-testing!