DateField: onChange not called on blur when date is invalid or incomplete

[pudek357]

Provide a general summary of the issue here

According to #9510, invalid or incomplete date values should not be emitted via onChange while typing, but should be emitted when the user blurs the field.
However, when the user blurs the field with an invalid or incomplete date, onChange is not called at all.

🤔 Expected Behavior?

• User enters valid date.
• User removes one of the segment (date become invalid)
• User blurs from the field
• onChange is called.

😯 Current Behavior

• User enters valid date.
• User removes one of the segment (date become invalid)
• User blurs from the field
• onChange is not called.

💁 Possible Solution

No response

🔦 Context

No response

🖥️ Steps to Reproduce

Add console log to onChange to TimeField example in https://react-aria.adobe.com/TimeField and test repro steps above, or use this link: https://stackblitz.com/edit/hazsexms-xrw2sxau?file=src%2FExample.tsx

Screen.Recording.2026-02-09.at.14.31.09.mov

[LFDanLu]

There is a bit of ambiguity in the description of that PR, but the intention was to emit onChange on blur of an invalid field if said invalid value would end up being coerced to a valid value (e.g. if a user entered Feb 29 in a year that isn't a leap year). However, if we cannot reasonably infer/clamp/coerce the provided value, such as in your reproduction where part of a time segment is deleted, then we don't fire onChange.

I could see an argument for firing null in that case instead, but then how would an app differentiate this incomplete blur case from the case where the user has fully cleared their field? If we were to clear all the segments on blur of a incomplete field, I could see that being poor UX for the end user if they intended to come back to the field and only wanted it to be incomplete temporarily.

Do you have a use case you can share where the current behavior is problematic?