Wrong unicode display after font resize

[LinoWhy]

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

wezterm 20230712-074712-5d1136d2

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

unicode "U+1F784" can be displayed correctly on start.
However it displays a square, once I change the font size. See the right side of the picture below.

To Reproduce

No response

Configuration

local config = {
  default_prog = { "wsl.exe", "--cd", "~" },
}

return config

Expected Behavior

No response

Logs

No response

Anything else?

No response

[wez]

Please try the latest release

[LinoWhy]

Still not fixed in 20240203-110809-5046fc22.

[wez]

Please run: wezterm ls-fonts --codepoints 1F784 and share the output

[LinoWhy]

output:

wezterm ls-fonts --codepoints 1F784
14:29:52.573  WARN   wezterm_font > No fonts contain glyphs for these codepoints: \u{1f784}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust your
configuration so that it can find them.
https://wezfurlong.org/wezterm/config/fonts.html has more information about configuring fonts.
Set warn_about_missing_glyphs=false to suppress this message.
LeftToRight
 0 🞄    \u{1f784}    x_adv=10 cells=1  glyph=.notdef,0    wezterm.font("JetBrains Mono", {weight="Regular", stretch="Normal", style="Normal"})
                                      C:\WINDOWS\FONTS\JETBRAINSMONO-REGULAR.TTF, DirectWrite

The picture below is a comparison between Windows Terminal & Wezterm.

[wez]

Sounds like the same underlying issue as in, where DirectWrite isn't telling us which font to use:

• No fonts contain glyphs for those codepoints: \u{1d4d2} #4768

the workaround is to explicitly list in your wezterm.font_with_fallback list the font that you know contains that codepoint.

[LinoWhy]

This still occurs with font Cascadia Code. But Windows Terminal with the same font setting doesn't have this issue.

It's weird that sometimes when I change the font size in Wezterm, it will show the correct glyphs ever before it's closed. But sometimes it doesn't.