Datepicker time changes do not fire onChange event unless user clicks "ok" button.

[mrfixij]

Describe the bug
When using the datepicker time component - the valueChanged callback is only called when the OK button is pressed and not when clicking outside of the popup to close it. This also leaves the state in a confusing place because value is not updated in the below example.

To Reproduce
Steps to reproduce the behavior:

1. Using the basic Define Hour datepicker as a template: update the code to the following.

    <RadzenLabel Text="Select Date" Component="DatePickerHourFormat" />
    <RadzenDatePicker TValue=DateTime? Value=@value ValueChanged=@OnValueChanged ShowTime="true" HourFormat="12" DateFormat="MM/dd/yyyy h:mm tt" Name="DatePickerHourFormat" />
    
</RadzenStack>
<EventConsole @ref=@console />

@code {
    DateTime? value = DateTime.Now;
    EventConsole console;
    private void OnValueChanged(DateTime? newValue)
    {
        console.Log(newValue); 
        value = newValue.Value;
    }
}

2. Open the datepicker, change the date. Observe that the console has logged the dateTime updating.
3. Open the datepicker. Change the time using the up/down arrows on the UI. Close the datepicker by clicking outside of the modal. Observe that the console has not logged the new time.
4. Repeat step 3, but close the datepicker by clicking the OK button instead. Observe that the console has logged the new time.

Expected behavior
When closing the modal without the OK button, the ValueChanged event should fire

[enchev]

This is intentional. When the Ok button is present value will be updated only when On button is pressed - if you set ShowTimeOkButton=false, value will be updated immediately. Changing this behavior will be a breaking change.

[Anspitzen]

Current behavior seems correct, butt display of data on cancle is wrong.
On close without changing the bound Value displayed Value should reset to real data bound value and not stay on (wrong because not set) internal component value.
Else User WILL be confused as why the order/Birthday/whatever is saved incorrectly, even if the input is showing their correct data. Just because they did not click OK. It will show they did input the correct date without ever doing confirm.

Thats at least how I would expect it to work

[mrfixij]

Anspitzen brings up the core problem better than I did. If the user clicks away (cancels) the visual component remains the same, and presents the illusion of their changes persisting, but the underlying model doesn't update. Either the Ok button should be generally ineffective and a placebo for the user, or the changes to time should be reverted internally on close.

[Anspitzen]

• Clicking any Date on the selection will set DateTime instantly (and fire Change Event) while keeping select open. Will also take unconfirmed time and set it, bypassing the OK here already
• Changing time will not fire Change event but display selected time on Component independent of the underlaying real bound value. Can understand to not fire here on change as it will trigger too often when scrolling through times.
  As mentioned by enchev hiding OK Button will set time instant on change and trigger Change Event quite often.
• writing time into main text area directly sets Value on focus lost (TextBox Change Event)
• Clicking OK will set Value and close selection
• Clicking outside of selection will close it without clearing wrong display data or persisting data to model

Proposed solution: Persist data when
no OK-Button -> on date select, direct input, or on close (instead of on OK. Ok already closes the selection, would trigger set there also on close)