U+FE1A sits in the Vertical Forms block and is
unassigned in the Unicode version ICU ships with, so its script is
USCRIPT_UNKNOWN. When a shaping cluster fails to find a
glyph, Blink picks the "most informative" code point in the cluster
as a hint for the next font fallback; HasLikelyScript
only excludes USCRIPT_COMMON and
USCRIPT_INHERITED, so USCRIPT_UNKNOWN wins
the hint and pins fallback to a font that has no glyphs for the
cluster's real neighbours. They draw as .notdef tofu. The box on
U+FE1A itself is correct; the bug is that it also
takes down the chess piece, trophy and musical symbol next to it.
Each line embeds a single U+FE1A (shown as
︚ in the source). On an affected Chrome the
character after the box turns into tofu even though the font would
otherwise cover it.
U+FE1A is expected; the tofu on the planet, math
alphanumerics, trophy, rocket, chess pieces and musical symbols that
follow is the bug.
HasLikelyScript excluding
USCRIPT_UNKNOWN. The chess row recovers; the box on
U+FE1A itself stays as a box, which is
correct. QA later showed the reporter's exact string still broke:
the hint list for its run is truncated to U+FE1A alone,
so there is nothing else for ChooseHintIndex to
pick.
ChooseHintIndex skips them, so the fallback cycle never
dead-ends. Top row: reporter's string on the patched build; bottom
row: same string without U+FE1A for
reference.