Open stephtr opened 3 years ago
Hello stephtr, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Describe the bug
When programatically setting a
RangeSelector
'sMinimum
andMaximum
property to the same value, the app's UI breaks and partially doesn't respond to user actions (like hovering over a button). This behaviour was either introduced by Community.Toolkit.WinUI.UI.Controls v7.0.3 (not present in v7.0.2) or Project reunion 0.8.0 (not present in 0.5.6).Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
After toggling the switch, the UI should still work. Instead, the
RangeSelector
loses its handles and the button doesn't respond to mouse events but needs to be reactivated via the keyboard's Tab.Screenshots
Environment
Additional context