Windows Terminal version

1.12.10982.0

Windows build number

10.0.19044.1645

Other Software

Cascadia Code 2111.01

Steps to reproduce

• Install static Cascadia Code PL Regular [1]:
  • ttf/static/CascadiaCodePL-Regular.ttf or
  • otf/static/CascadiaCodePL-Regular.otf
• Use it as font with 12 pt
• Utilize the powerline glyphs like so (copy and paste into command prompt terminal window):
  set prompt=$E[0;33;40m$E[7;33;40m Manuel $E[0;33;40m$E[7;32;40m  ~ $E[0;32;40m$E[7;34;40m  $E[0;34;40m$E[0;37;40m $g

[1] https://github.com/microsoft/cascadia-code/releases/tag/v2111.01

Expected Behavior

The upper and lower 'border' of the powerline glyphs shall line up with the 'cell' top and bottom.
Cell top and bottom can be seen if insert a blank with reverse colors (like done in the prompt command above).

This is how it should look like, roughly (magnified 400%):

Actual Behavior

The glyphs are about 1 pixel to small vertically; here with the otf one pixel at the bottom seems to be missing:

This is most notable with the rounded D shape powerline symbols, but in fact are present in all.

The static ttf seem to have the missing pixel in the top.
I did not try the VF.

Origin of issue: Bottom (after closing) ryanoasis/nerd-fonts#828

I believe this is not a Cascadia Code issue, because the original issue came up with a Nerd Font patched version of that font (Caskaydia Cove); and in the process of that issue I tried a lot like ascent and descent changing (all of them OS/2, typo, Win etc ;), PPEM modification, etc pp, all to no avail.
I do not really know how Windows Terminal finds out its cell size. If one understands that maybe the font can be beat into function. But I fear that it is a rendering issue, as this is always 1 px big, regardless of font size in point.

Edit: Fix typo