NumericUpDown value going out of async with bound value

[corvinsz]

Bug explanation

as described in #3781 there is a problem where the Value of the Numeric-/DecimalUpDown control can go out of sync with the bound property in a viewmodel.

Steps to reproduce:

1. Set the Maximum of the UpDown control to any value
2. Set the Value equal to the Maximum
3. Enter a new Value greater than the Maximum

I will later try and add a failing test for this.

Edit

@Keboo I created a branch (fixNumUpDownCoerceToMax)) which is trying to reproduce the bug, however I can't get it to work. Whenever I call any method on the numericUpDown control the test is crashing.
I'm not too familiar with your XamlTest Library, it could be that I have set up something wrong.
The problem starts in NumericUpDownTests.cs line 179. It would be great if you had a look at this😊

Version

current main branch

[corvinsz]

fixed in #3787