You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MenuFlyout text color has the wrong theme when the IsEnable property is changed in CodeBehind and the application theme is different from the OS theme
#9662
I created a button with a MenuFlyout with three MenuFlyoutItem. When I click the first one, the next two switch to the Disabled state. However, when the application theme is different from the OS theme, the text is the wrong color.
Steps to reproduce the bug
1- I created a button with a MenuFlyout with three MenuFlyoutItem.
2- Create a click event on the first MenuFlyout item that changes the IsEnable property to false.
3- Put a different theme in your application than the OS theme.
Expected behavior
The color of the text must be in accordance with the theme, fully visible.
Screenshots
NuGet package version
Windows App SDK 1.5.3: 1.5.240428000
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 2004 (19041, May 2020 Update)
IDE
Visual Studio 2022
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I created a button with a MenuFlyout with three MenuFlyoutItem. When I click the first one, the next two switch to the Disabled state. However, when the application theme is different from the OS theme, the text is the wrong color.
Steps to reproduce the bug
1- I created a button with a MenuFlyout with three MenuFlyoutItem.
2- Create a click event on the first MenuFlyout item that changes the IsEnable property to false.
3- Put a different theme in your application than the OS theme.
Expected behavior
The color of the text must be in accordance with the theme, fully visible.
Screenshots
NuGet package version
Windows App SDK 1.5.3: 1.5.240428000
Packaging type
Packaged (MSIX)
Windows version
Windows 10 version 2004 (19041, May 2020 Update)
IDE
Visual Studio 2022
Additional context
No response
The text was updated successfully, but these errors were encountered: