UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Example URL:
https://en.wikipedia.org/wiki/Alphabetic_Presentation_Forms

Steps to reproduce the problem:
1. Navigate to the page specified
2. Notice the character renders with 0 width
3. This is correct (probably?).
4. If a custom webfont is used with the same character code the width is still rendered with 0. Even if the bounding box is set (tried with TTF/Woff/Woff2).

What is the expected behavior?
The webfont loaded using unicode FB1E or Entity ‬ should render with the webfont's bounding box not 0.

Edge renders with the correct width of the bounding box.

What went wrong?
It appears that Chrome has somehow "hardcoded" the width of this specific unicode character to 0.

In the attached zip search for "origin" or "FB1E" to see the broken bounding box.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.92  Channel: stable
OS Version: 10.0
Flash Version: 

This is the only unicode I can see it happening with in the \F000 - \FBB8 (3000 characters) range I'm testing with right now.
 

Deleted: example.zip 1.3 MB

example.zip 1.3 MB Download