New issue
Advanced search Search tips

Issue 738951 link

Starred by 1 user
Status: Duplicate
Merged: issue 628820
Owner: ----
Closed: Aug 2017
Cc:
msw@chromium.org
asvitk...@chromium.org
drott@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 3
Type: Bug

Blocking:
issue 454835



Sign in to add a comment

RenderTextHarbuzz: The string "⎷😊" isn't broken into 2 runs

Project Member Reported by tapted@chromium.org, Jul 4 2017 
Chrome Version       : 61.0.3147.0
OS Version: OS X 10.12.5

Currently this means Tofu for mac, or a sub-optimal font fallback on Windows.

"⎷ 😊" renders fine if there's a space between.

The glyph I get for "⎷" is pretty peculiar in most places, so this specific string might not be interesting, but there may be some underlying problem.
windows_nospace.png
4.4 KB View Download
windows_space.png
4.3 KB View Download
cocoa.png
14.2 KB View Download
rthb-mac-old-nospace.png
4.4 KB View Download
rthb-mac-old-space.png
5.0 KB View Download
rthb-mac-canary-nospace.png
5.0 KB View Download
rthb-mac-canary-space.png
5.2 KB View Download

Comment 1 by tapted@chromium.org, Jul 4 2017 

I wonder if we could automatically break runs the first time we encounter a missing glyph using the result of GetFallbackFont. Then just call it again, starting from the missing glyph (and move ahead at least one character). At least on Mac, CTFontCreateForString doesn't seem to cater for any interesting characters after the first one it finds.

Comment 2 by tapted@chromium.org, Jul 6 2017

Blocking: 454835

Comment 3 by behdad@chromium.org, Jul 10 2017

Cc: drott@chromium.org
This looks like same issue as https://bugs.chromium.org/p/chromium/issues/detail?id=739641 to me.  Or rather, that one is a dupe of this.

Maybe drott@'s Emoji iterator can be incorporated here to help with font selection.

Comment 4 by tapted@chromium.org, Aug 22 2017

Mergedinto: 628820
Status: Duplicate (was: Available)
►

Sign in to add a comment