Issue 454108 in chromium:   in some fonts is displayed as symbol

509 views
Skip to first unread message

chro...@googlecode.com

unread,
Jan 31, 2015, 1:26:38 PM1/31/15
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-Content Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 454108 by dzinta...@gmail.com:   in some fonts is displayed
as symbol
https://code.google.com/p/chromium/issues/detail?id=454108

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/40.0.2214.94 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. see attached screenshot

What is the expected behavior?

What went wrong?
html special character   in some fonts is displayed as some symbol
(see attachment)

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A

Did this work before? Yes week ago it worked

Does this work in other browsers? Yes

Chrome version: 40.0.2214.94 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 16.0 r0

Attachments:
google-chrome-problem.png 84.0 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Feb 1, 2015, 3:51:17 PM2/1/15
to chromi...@chromium.org

Comment #1 on issue 454108 by sandy.mc...@a8c.com:   in some fonts is
This is happening as well on Mac OS 10.10.2.

Chrome Version 40.0.2214.94 (64-bit)

I also tested in Chromium Version 42.0.2293.0 (64-bit)
and Canary Version 42.0.2292.0 canary (64-bit)

Font Eigerdals from TypeKit seems to display a "-"
Font Brandon Grotesque from TypeKit seems to display a "`"
Font Neuton from Google Fonts seems to display a blank character much wider
than a normal space.

I've heard of other reports as well, but these are the three I have
personally tested.

chro...@googlecode.com

unread,
Feb 3, 2015, 12:07:30 AM2/3/15
to chromi...@chromium.org
Updates:
Labels: -Cr-Content Cr-Blink-Fonts

Comment #2 on issue 454108 by tk...@chromium.org:   in some fonts is
(No comment was entered for this change.)

chro...@googlecode.com

unread,
Feb 3, 2015, 5:50:13 AM2/3/15
to chromi...@chromium.org

Comment #4 on issue 454108 by ericvanb...@gmail.com:   in some fonts
I just noticed a problem with a font too which may be related.

A client has the Aller font embedded
(http://www.fontsquirrel.com/fonts/aller). No break spaces seem not to be
rendered at all. May be just like the other examples a wrong glyph but this
one simply has no width.

chro...@googlecode.com

unread,
Feb 3, 2015, 5:53:12 AM2/3/15
to chromi...@chromium.org

Comment #5 on issue 454108 by ericvanb...@gmail.com:   in some fonts
Do you accept a zip with html and fonts for triage?

chro...@googlecode.com

unread,
Feb 3, 2015, 6:02:13 AM2/3/15
to chromi...@chromium.org

Comment #6 on issue 454108 by manoranj...@chromium.org:   in some
yes, please provide HTML sample for the repro.

Thank you!

chro...@googlecode.com

unread,
Feb 3, 2015, 6:11:11 AM2/3/15
to chromi...@chromium.org

Comment #7 on issue 454108 by ericvanb...@gmail.com:   in some fonts
Sample attached.

Further info:

- The issue is not present in v37 and considering the reports I received it
was most likely introduced in v40.
- The issue occurs regardless of the format used (woff, woff2 or ttf)

Attachments:
FontIssueSample.zip 157 KB

chro...@googlecode.com

unread,
Feb 3, 2015, 12:05:41 PM2/3/15
to chromi...@chromium.org

Comment #8 on issue 454108 by dzinta...@gmail.com:   in some fonts is
Html sample is attached

Attachments:
demo (kopija).html 580 bytes

chro...@googlecode.com

unread,
Feb 4, 2015, 5:55:26 AM2/4/15
to chromi...@chromium.org
Updates:
Status: Assigned
Owner: e...@chromium.org
Cc: p...@chromium.org
Labels: -OS-Windows -Needs-Feedback OS-All M-42

Comment #9 on issue 454108 by manoranj...@chromium.org:   in some
Thanks for providing sample HTML file. I am able to reproduce this issue on
ALL OS and below is the bisect information.

Chromium CL:
============
https://chromium.googlesource.com/chromium/src/+log/40.0.2212.0..40.0.2214.0?pretty=fuller&n=10000

Blink CL:
=========
https://chromium.googlesource.com/chromium/blink/+log/de60d289c850e1601ca11fb7ad08fb327f3f51d5..33445762977cec86f2fff85da34f01ca132858fa?pretty=fuller&n=10000

eae@, could you please look into this blink change
(https://chromium.googlesource.com/chromium/blink/+/74ee4e87ddd8c43ea6ce8064a1bc2b83b9abcaaf)?

Thank you!

chro...@googlecode.com

unread,
Feb 6, 2015, 7:42:08 AM2/6/15
to chromi...@chromium.org

Comment #10 on issue 454108 by milestoj...@gmail.com:   in some fonts
Hello

I am having the same problem.

http://stackoverflow.com/questions/28362582/nbsp-is-displayed-as-colon-on-google-chrome

Is there anyway this can be solved?

chro...@googlecode.com

unread,
Feb 6, 2015, 7:50:10 AM2/6/15
to chromi...@chromium.org

Comment #11 on issue 454108 by milestoj...@gmail.com:   in some fonts
I am having the similar problem.

chro...@googlecode.com

unread,
Feb 8, 2015, 10:13:57 PM2/8/15
to chromi...@chromium.org

Comment #14 on issue 454108 by ko...@chromium.org:   in some fonts is
Issue 451933 has been merged into this issue.

chro...@googlecode.com

unread,
Mar 3, 2015, 9:27:26 PM3/3/15
to chromi...@chromium.org

Comment #16 on issue 454108 by ko...@chromium.org:   in some fonts is
Adding some data point:
This is happening on M40+ Android Chrome, in my case on Nexus5 with
Japanese locale.
(This case,   is displayed as "・" (middle-dot).)

  seems often used for adjusting layouts, and they are pretty visible
in Japanese locale, I guess this is affecting most of Android users (10+M?).

chro...@googlecode.com

unread,
Aug 17, 2015, 11:54:47 PM8/17/15
to chromi...@chromium.org

Comment #18 on issue 454108 by alexandr...@gmail.com:   in some fonts
So what's the solution then???

chro...@googlecode.com

unread,
Aug 18, 2015, 10:28:07 PM8/18/15
to chromi...@chromium.org

Comment #20 on issue 454108 by ko...@chromium.org:   in some fonts is
In Japanese locale, on Android (I tested Lollipop on Nexus 4 & 6),
if page's locale is Japanese (e.g. <html lang="ja">) then "MotoyaLMaru" is
the preferred font for displaying contents, and its &nbsp (U+00A0) seems to
be the middle-dot.

If page's locale is not "ja", some other font ("Roboto" or "Noto") is used
and the problem isn't exposed (whitespace is displayed).

I checked what glyph is available in MotoyaLMaru, and it seems the glyph
is not available for U+00A0(see the attached screenshot of fontforge).
So some fallback glyph is displayed?

FYI The information of the font file is available at e.g.
https://fontinfo.opensuse.org/fonts/MotoyaLMaruW3Mono.html

Attachments:
fontforge_MTLmr3m.ttf_nbsp.png 83.1 KB

chro...@googlecode.com

unread,
Aug 19, 2015, 1:07:54 AM8/19/15
to chromi...@chromium.org

Comment #21 on issue 454108 by taken...@google.com: &nbsp; in some fonts is
I guess the middle-dot in question is ".notdef" glyph in MotoyaLMaru?

chro...@googlecode.com

unread,
Aug 19, 2015, 1:15:37 AM8/19/15
to chromi...@chromium.org

Comment #22 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
#21 looks like so.

Attachments:
fontforge_motoya_notdef.png 116 KB

chro...@googlecode.com

unread,
Aug 20, 2015, 2:13:37 PM8/20/15
to chromi...@chromium.org

Comment #23 on issue 454108 by e...@chromium.org: &nbsp; in some fonts is
Interesting, it is supposed to always fall back on the space glyph if the
nbsp glyph isn't available. Thanks!

chro...@googlecode.com

unread,
Aug 25, 2015, 11:28:56 PM8/25/15
to chromi...@chromium.org

Comment #24 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
I tried the Motoya font[1] as a webfont on Ubuntu to see how it reproduces,
but &nbsp; fell back to "TakaoPGothic" on my environment (checked via
Inspector's
computed style). So it is working as expected?

My current hypothesis is that on Android, it still fails to find a glyph
deep in the font fallback path, and picked an undesired one.

<!doctype html>
<style>
@font-face {
font-family: 'motoya';
src: url('/MTLmr3m.ttf');
}
div { font-family: 'motoya'; }
</style>
<div>This&nbsp;is&nbsp;a&nbsp;pen.</div>

[1]
https://github.com/android/platform_frameworks_base/blob/21e6e2de1f0062f949fcc52d0b4559dfa3246e0e/data/fonts/MTLmr3m.ttf

chro...@googlecode.com

unread,
Aug 26, 2015, 12:22:02 AM8/26/15
to chromi...@chromium.org
Updates:
Cc: ko...@chromium.org

Comment #25 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
(No comment was entered for this change.)

chro...@googlecode.com

unread,
Aug 26, 2015, 8:03:29 AM8/26/15
to chromi...@chromium.org

Comment #26 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
Tentative fix:
https://codereview.chromium.org/1317833003/

chro...@googlecode.com

unread,
Aug 27, 2015, 2:28:24 AM8/27/15
to chromi...@chromium.org
Updates:
Status: Started
Owner: ko...@chromium.org
Cc: e...@chromium.org

Comment #27 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
(No comment was entered for this change.)

chro...@googlecode.com

unread,
Aug 27, 2015, 4:05:29 AM8/27/15
to chromi...@chromium.org

Comment #28 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
I'll work on the Japanese locale issue.

Others (some fonts show some glyph or nothing for &nbsp;) are working as
expected,
so if it's still an issue, maybe some whitelisting or special casing will be
necessary.
For that part, I'd like to defer to someone who wants to take it.

chro...@googlecode.com

unread,
Aug 27, 2015, 8:34:19 PM8/27/15
to chromi...@chromium.org

Comment #29 on issue 454108 by bugd...@chromium.org: &nbsp; in some fonts
is displayed as symbol
https://code.google.com/p/chromium/issues/detail?id=454108#c29

The following revision refers to this bug:
http://src.chromium.org/viewvc/blink?view=rev&rev=201348

------------------------------------------------------------------
r201348 | ko...@chromium.org | 2015-08-28T00:27:15.154636Z

Changed paths:
M
http://src.chromium.org/viewvc/blink/trunk/Source/platform/fonts/Font.cpp?r1=201348&r2=201347&pathrev=201348

Fix &nbsp; fallback glyph lookup

On Japanese locale Android which has Motoya Maruberi
as the system default font (up until 5.1), the font
fallback path mistakenly picked up ".notdef" glyph
for &nbsp; (U+00A0).

This happened because in the fallback path it still
ended up in looking up non-existent glyph in the same
font file and fell back to the "missingGlyphData".

This is because Blink looks up the glyph in
normalized codepoint (for U+00A0, normalized to U+0020)
but still it tries to look up the original codepoint.

This bug was exposed by the following change, to make
not to normalize &nbsp; to space before looking up glyph.
https://codereview.chromium.org/705163003

BUG=454108

Review URL: https://codereview.chromium.org/1317833003
-----------------------------------------------------------------

chro...@googlecode.com

unread,
Aug 28, 2015, 1:31:56 AM8/28/15
to chromi...@chromium.org

Comment #31 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
Okay - so Japanese locale Android's &nbsp; issue is "Fixed", but
for other fonts / webfonts that has some glyph or zero width space
for &nbsp; - it's "WontFix" as it is working expected.

But the issue still remains, so for tracking purpose I filed a separate
issue 525890.

chro...@googlecode.com

unread,
Aug 28, 2015, 1:35:57 AM8/28/15
to chromi...@chromium.org
Updates:
Status: Started
Labels: -Pri-2 Pri-1 Merge-Request-46

Comment #32 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
As the fix is relatively small and should be safe.
Considering the impact on most Japanese locale Android phones,
I think this is worth merging to M46 to make it available as early as
possible.

TPMs, if it looks okay for several days after dev channel Chrome for
Android is out,
could you consider approving merge of this change to M46?

chro...@googlecode.com

unread,
Aug 31, 2015, 12:58:49 AM8/31/15
to chromi...@chromium.org
Updates:
Labels: -Merge-Approved-46 merge-merged-2490

Comment #34 on issue 454108 by bugd...@chromium.org: &nbsp; in some fonts
is displayed as symbol
https://code.google.com/p/chromium/issues/detail?id=454108#c34

The following revision refers to this bug:
http://src.chromium.org/viewvc/blink?view=rev&rev=201463

------------------------------------------------------------------
r201463 | ko...@chromium.org | 2015-08-31T04:52:12.620442Z

Changed paths:
M
http://src.chromium.org/viewvc/blink/branches/chromium/2490/Source/platform/fonts/Font.cpp?r1=201463&r2=201462&pathrev=201463

Merge 201348 "Fix &nbsp; fallback glyph lookup"

> Fix &nbsp; fallback glyph lookup

> On Japanese locale Android which has Motoya Maruberi
> as the system default font (up until 5.1), the font
> fallback path mistakenly picked up ".notdef" glyph
> for &nbsp; (U+00A0).

> This happened because in the fallback path it still
> ended up in looking up non-existent glyph in the same
> font file and fell back to the "missingGlyphData".

> This is because Blink looks up the glyph in
> normalized codepoint (for U+00A0, normalized to U+0020)
> but still it tries to look up the original codepoint.

> This bug was exposed by the following change, to make
> not to normalize &nbsp; to space before looking up glyph.
> https://codereview.chromium.org/705163003

> BUG=454108

> Review URL: https://codereview.chromium.org/1317833003

TBR=ko...@chromium.org

Review URL: https://codereview.chromium.org/1316213004
-----------------------------------------------------------------

chro...@googlecode.com

unread,
Aug 31, 2015, 2:12:07 AM8/31/15
to chromi...@chromium.org
Updates:
Status: Fixed

Comment #35 on issue 454108 by ko...@chromium.org: &nbsp; in some fonts is
displayed as symbol
https://code.google.com/p/chromium/issues/detail?id=454108

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages