Skip to content

WASM: 'Segoe UI' not observed if UnoDefaultFont is set to None (Windows) #19636

Open
@remokeitel

Description

@remokeitel

Current behavior

  • font-family style is set to 'font-{random_number}'
  • @font-face definition for 'Segoe UI' in Fonts.css is ignored

Expected behavior

  • font-family style is set to 'Segoe UI' or 'Segoe UI Variable'
  • @font-face definition for 'Segoe UI' in Fonts.css is used

How to reproduce it (as minimally and precisely as possible)

  • create default Uno.Sdk project
  • set UnoDefaultFont to None
  • start app as WebAssembly in Windows

Workaround

  • overwrite all Style and FontFamily resources, where font family is set to XamlAutoFontFamily in themeresources.xaml (which are resolved in WinUI 3 app as 'Segoe UI Variable' and not 'Segoe UI'), e. g. <wasm:FontFamily x:Key="ContentControlThemeFontFamily">Segoe UI</wasm:FontFamily>

Works on UWP/WinUI

Yes

Environment

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

No response

Affected platforms

WebAssembly

IDE

Visual Studio 2022

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    difficulty/tbdCategorizes an issue for which the difficulty level needs to be defined.kind/bugSomething isn't workingtriage/untriagedIndicates an issue requires triaging or verification

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions