TextBox: Wrong font stretch when setting font family

[ceee]

Describe the bug
When you set a font family via FontFamily in a TextBox it may use the wrong font stretch by default, in case the font family contains multiple stretches.
This is the case for Arial, Bahnschrift and others.
There is no way to select a different font stretch in a TextBox as the FontStretch property seems to be completely ignored.
The same problem also exists for the RichEditBox.

Steps to reproduce the bug

1. Create a new UWP project
2. Add this XAML into the MainPage.xaml

<StackPanel HorizontalAlignment="Center" VerticalAlignment="Center">
  <TextBlock Text="Arial" FontFamily="Arial" FontSize="32" />
  <TextBox Text="Arial" FontFamily="Arial" FontSize="32" FontStretch="Normal" Margin="0 20 0 0" Width="300" />
</StackPanel>

Expected behavior
It is expected that the rendered text from the TextBlock looks the same as from the TextBox. Instead Arial Narrow is used and the FontStretch property is completely ignored.

Screenshots

Version Info
OS: Win10 Pro x64 (17763)
SDK: Reproduced this with 17763, 17134, 16299 and 15063.

[ceee]

Any updates on this?

[ceee]

Ping ping... @chrisglein

[marcelwgn]

I think this is something we can only fix with WinUI 3.0 since settting the font stretch on the content presenting ScrollViewer has no effect, and changing the content presenting ScrollViewer to a ContentPresenter and setting thats FontStretch does not work either.

[chrisglein]

Confirmed. Neither TextBox.FontStretch or RichEditBox.FontStretch are not setting this with RichEdit. This is a bug, and to fix it we'd need to do it in WinUI 3.0. For RichEditBox as a workaround the app can set it in code through the document API on CharacterFormat using the ITextCharacterFormat API.

[ceee]

Still broken in WinUI 3.0 Preview 2, @chrisglein @chingucoding @jevansaks

[DierkDroth]

Still broken after releasing WindowsAppSdk. Confirmed with TextBox/TextBlock + Roboto font.

[ceee]

Almost 3 years later and this is still ignored 😔
@chrisglein As this was not part of WinUI 3, when and where can we expect a fix for this issue?

[ceee]

@jevansaks @chrisglein Any updates on this issue?

[AndrewKeepCoding]

I'd really appreciate if this get fixed soon.😢

[ceee]

@jevansaks @chrisglein Any updates on this issue?

[JohnnyWestlake]

Bumping this; I also don't understand why you would need WinUI 3 to fix it. It's an internal platform issue...