1️⃣ through 9️⃣ and #️⃣ aren't rendering properly in Chrome/Edge

[tannerlyons]

Describe the bug

This font contains a glyph for U+20E3. Because that character is part of the keycap emoji ligature, and ligatures don't render unless every character is in the same font, Chrome isn't able to fall back to the system emoji font to render the whole ligature.

[edit]: OK I don't actually think I know enough about fonts to assert the previous statement as the cause of this bug. This is what I believe is happening though and I hope font experts can take it from here.

The only solution we've found so far is to monkeypatch the font and delete the glyph. Any other suggestions would be appreciated.

To Reproduce
Steps to reproduce the behavior:

1. Use Inter in chrome
2. Try and render the emoji 1️⃣ through 9️⃣ and #️⃣

See the repro: https://codesandbox.io/s/white-pine-hiwyf?file=/index.html

Expected behavior

The use of the font in Chrome should still allow 1️⃣ through 9️⃣ and #️⃣ to render properly.

Screenshots

In code:

Rendered:

Environment

• OS: OSX, Windows, and Ubuntu were tested.
• App that renders the font: Chrome
• Version of font: 3.018;git-588b23468

Additional context

• This was a problem in 3.15 as well, but we haven't looked further back than that.
• Firefox and other browsers seem to be fine

[tannerlyons]

This is also happening in Edge

[rsms]

I'd say this is a "bug" (or rather "odd behavior") in chromium rather than a bug in Inter, since other software seems to do the right thing.

Chromium: (broken)

Firefox: (correct)

Safari: (correct)

(Edge is chromium so that's why it looks broken in Edge.)

My best guess is that this is an issue stemming from Harfbuzz which Chromium uses for text shaping.

However, I think the solution here is to remove glyph uni20E3 and mapping to U+20E3 as it's an old and probably unused glyph.

[rsms]

[rsms]

Once this lands in a new release you can try it here:
https://rsms.me/inter/lab/?sample=%23%EF%B8...

[rsms]

This has been released with v3.19

[tannerlyons]

Woop woop! Thanks @rsms!!