RangePicker clicks on a different area to close the date box for a bug that triggers the onChange event of the old value

RangePicker 点击其他区域关闭日期框会触发返回一个旧值的OnChange事件的BUG，如下图所示：

RangePicker Clicking on another area to close the date box triggers a BUG that returns an old Value OnChange event, as shown in the following figure:

只有按下拉框里的确定按钮关闭才不会触发旧的Onchange事件

Only pressing the OK button in the drop-down box to close does not trigger the old Onchange event

所以点击其他区域关闭日期框是不是不应该触发一个Onchange?

So clicking on other areas to close the date box shouldn’t trigger an Onchange?

code： <RangePicker OnChange="OnDatePickChange" AllowClear="@false" Value="@(new DateTime?[] {)" TValue="DateTime?[]" ShowTime='@("HH:mm")' Format="MM-dd HH:mm"/>

[Alexbits]

But now there is no way for me to get the latest value, because the value returned by the onchange event is messy, how do I get the latest value instead of letting it be restored?

Maybe it’s possible to come up with an API to set it up?

@Alexbits

@GlodenBoy Please read the above and wait a bit while the OnChange behavior will be fixed.

[Alexbits]

@Alexbits

I think clicking on a date triggers an Onchange event is right, I just don’t understand that clicking on an empty area to close the drop-down date box after I’ve selected 2 dates will trigger an Onchange event with the wrong value, which shouldn’t need to be triggered because the values have already been changed.

@GlodenBoy The OnChange should not be triggered by the closed dropdown. This will be fixed.

Should the behavior of clicking on an empty area to close the drop-down box be consistent with the behavior of the OK button?

No, it should not have the same behavior as the OK button. It reverts the value to the previous one or clears it if not confirmed with the OK button.