TimeRangeField: allow time ranges that cross midnight (e.g. 22:00 → 06:00)?

[abouletwiiisdom]

Hi! I'd like to hear how others handle this case with TimeRangeField.

Current behavior

TimeRangeFieldRoot compares start and end as times on the same day. When end is before start, isInvalid is true (the !isBeforeOrSame(start, end) check). The value is still emitted, but every segment gets aria-invalid="true" and data-invalid. As far as I can tell (2.11.0), no prop changes this.

Our case

We use a time range to define a daily window in which a recurring task is allowed to run. A window that crosses midnight is valid for us: 22:00 → 06:00 means "from 10 PM until 6 AM the next morning", and our backend already handles it.

With TimeRangeField, this works functionally, but screen readers announce the range as invalid, and it would look like an error as soon as data-invalid is styled. For now we use two separate TimeFields instead.

Question

Should TimeRangeField support this? Some ideas, open to others:

• an opt-in prop that skips the start/end order check for ranges that wrap around midnight
• a way to customize the range validation (e.g. a callback)
• or two TimeFields is the recommended approach for this case

Thanks!