Numeric range logic

Hello @Team.

If you change the minimum or maximum properties on the fly, the value will not respect this change. Here's an example:


<RadzenNumeric @bind-Value=@(Minimum) Max="10" Min="0" />
<RadzenNumeric @bind-Value=@(Maximum) Max="10" Min="@(Minimum)"/>

The way I see it, the value has to be always between the [Min, Max] range. So if either limit is updated, the value should be rechecked and, if out of range, updated with the nearest lower/upper limit value. What are your thoughts on this?

Hi @kim,

Yes, we can do that.

1 Like