Probably a small bug : a new Date instance (instead of a different date) is needed to trigger ‘onChange’ when calling setValue on a DatePicker :
Yep, will be fixed in the next update. Thanks for pointing the issue.
Currently, datepicker reacts on the new date object, it doesn’t check the real date value in the object.