DateTimePicker is reporting as invalid after setting a valid value programmatically if it was previously invalid

[davidef]

Description

DateTimePicker is reporting as invalid after setting a valid value programmatically if it was previously invalid (for example the user before selected only the date)

Expected outcome

the status should be valid after programmatically set a valid value

Minimal reproducible example

DateTimePicker dateTimePicker = new DateTimePicker();
dateTimePicker.addValueChangeListener(e -> {
	Notification.show("value change: " + e.getValue());
});
add(dateTimePicker);

Button setValidValue = new Button("Set valid value");
setValidValue.addClickListener(e -> {
	dateTimePicker.setValue(LocalDateTime.of(2000, 1, 1, 1, 0));
});
add(setValidValue);

Button checkValid = new Button("Check valid");
checkValid.addClickListener(e -> {
	Notification.show("Is invalid: " + dateTimePicker.isInvalid());
});
add(checkValid);

Steps to reproduce

1. Select only the date
2. The field is as expected invalid
3. Set a valid value programmatically
4. The field report that is invalid but it instead it contains a valid value

Environment

Vaadin version(s): 25.0.3

Browsers

Issue is not browser related

[yuriy-fix]

The issue seems to be valid and is verified in the Vaadin docs. It differs from the behaviour of text-field. We need to take a closer look at cases where the value is set programmatically, for example when setting an initial value.