Hi Peter,
The reason the behavior changed from v3.0.1.6 to v3.2.1.0 is that there was a bug in v3.0 that prevented the minimum value from being enforced.
The new behavior is the correct behavior. We realize that it has limitations, but we have considered the alternatives and this is the best option.
Please refer to the Resolution section of
Defect #318 for a more detailed explanation.
Regards,
Gregory Austin
Syncfusion Inc.