Open carldebilly opened 7 months ago
Yup. We're taking this as a breaking change in Uno 6. See https://github.com/unoplatform/uno/pull/15684
There shouldn't be any bugs caused by this though. Just wrong terminology being used.
Note that the precedences enum isn't intended for public access, even if it's public.
Current behavior
The current precedences mechanism is not following its own logic, especially when applying values coming from default style (defined in generic.xaml), implicit style (keyless resolved through resource dictionaries) and explicit style (keyed style referenced directly on the element).
TLDR
The default style is always saved under the
ImplicitStyle
precedence and the applied style (implicit or explicit) is saved under theExplicitStyle
precedence.Observed result
Building the following code:
In generic.xaml:
In app.xaml (AppResources.xaml)
Used like that in the MainPage.xaml:
Observed Result
Expected behavior
Expected Result
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
No
Environment
Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
NuGet package version(s)
Uno 5.1
Affected platforms
WebAssembly, Android, iOS, macOS (AppKit), Mac Catalyst, Skia (WPF), Skia (GTK on Linux/macOS/Windows), Skia (Linux Framebuffer)
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response