feat: Support entering invalid dates in DateField and constrain on blur #9510

devongovett · 2026-01-22T20:07:42Z

Fixes #3256, fixes #5965, closes #8385, fixes #6004

This is a slimmed down version of #8385 (thanks @boutahlilsoufiane for getting it started!). It refactors the way state is stored in useDateFieldState to use a new IncompleteDate class instead of types from @internationalized/date. This lets us temporarily store incomplete or invalid date values where some of the fields are null or represent dates or times that don't exist (e.g. February 31st, or 2am during a forward DST transition).

Instead of constraining the value immediately as the user types, these values are not emitted via onChange until the user blurs, at which point we constrain to a valid date. This lets users more easily edit dates that are temporarily invalid, e.g. when changing the day before the month. We still emit onChange in real time whenever possible, but not when the displayed date is invalid or incomplete.

Since Intl.DateTimeFormat cannot format invalid dates, we only use it to get the expected order of the fields, and then format the individual segments with Intl.NumberFormat.

This refactor also enabled entering zeros in all fields, even when zero is not a valid value (e.g. month/day). Doing this for 12 hour time required making IncompleteDate represent time in the user displayed hour cycle rather than always storing it in 24 hour time. This way we can store zero as a value and distinguish it from 12am.

rspbot · 2026-01-22T20:10:38Z

Build successful! 🎉

devongovett · 2026-01-22T20:13:17Z

packages/@react-stately/datepicker/src/useDateFieldState.ts

+      case 'hour': {
+        // TODO: in the case of a "fall back" DST transition, the 1am hour repeats twice.
+        // With this logic, it's no longer possible to select the second instance.
+        // Using cycle from ZonedDateTime works as expected, but requires the date already be complete.


Edge case! Previously you could enter 11/7/2021, 1:00 AM PST by first entering 11/7/2021, 1:00 AM PDT and then incrementing the hour field to switch from PDT to PST (try it here), but now that's impossible.

We could potentially check if the value is already complete (meaning we have all of the date fields and the hour), and in that case delegate to ZonedDateTime to handle the cycling. But it's impossible if we don't know the date yet – the user would need to enter everything and then go back and press the up arrow. Should we handle this case?

maybe related, but in the TimeField 12hr, if it's empty with just the "AM", then clicking that and pressing "up arrow" causes it to set the hours to "12" and takes a second press to get it to cycle to "PM"

This was also the case before but I refactored the way time is stored anyway to support entering zeros.

snowystinger

~~In TimeField s2 storybook it's displaying "AM" as "am" lowercase. In the s2 docs though, it's displaying correctly~~
Locale difference moving from US to AUS

In TimeField 12hr, aria-valuemin is 0 and valuemax is 11, but i think it should be 1-12? This is pre-existing.

<TimeField hourCycle={12} placeholderValue={new Time(20, 30, 0)} />

For some reason this is displaying blank, just dashes. Using ArrowUp on the hour field will show 8 though, and the display of pm is correct

packages/@react-stately/datepicker/src/useDateFieldState.ts

snowystinger · 2026-01-22T21:32:03Z

packages/@react-stately/datepicker/src/useDateFieldState.ts

+      case 'hour': {
+        // TODO: in the case of a "fall back" DST transition, the 1am hour repeats twice.
+        // With this logic, it's no longer possible to select the second instance.
+        // Using cycle from ZonedDateTime works as expected, but requires the date already be complete.


maybe related, but in the TimeField 12hr, if it's empty with just the "AM", then clicking that and pressing "up arrow" causes it to set the hours to "12" and takes a second press to get it to cycle to "PM"

packages/@react-stately/datepicker/src/useDateFieldState.ts

devongovett · 2026-01-23T17:14:22Z

@snowystinger

In TimeField 12hr, aria-valuemin is 0 and valuemax is 11, but i think it should be 1-12? This is pre-existing.

I did change this to be 1-12 but it's sort of incorrect because really 12 is the minimum and 11 is the maximum (12 hour time is weird). Noticed that chrome's native date picker does set it like this though.

For some reason this is displaying blank, just dashes. Using ArrowUp on the hour field will show 8 though, and the display of pm is correct

I think because you set a placeholderValue, not a value/defaultValue, so it doesn't display.

devongovett · 2026-01-23T17:19:22Z

packages/@react-stately/datepicker/src/useDateFieldState.ts

+    displayValue = new IncompleteDate(calendar, hourCycle, calendarValue);
+    setLastValue(calendarValue);
+    setLastCalendar(calendar);
+    setLastHourCycle(hourCycle);


If we want to support the case where the user starts entering a date/time, and then changes the calendar/hour cycle before completing it, we will need more complex logic here. Right now, this would simply reset the display value back to the current props.value rather than converting the partially entered value (which may be impossible in some cases).

feel like that's fine. don't think a lot of people are switching calendars or hour cycles in between

rspbot · 2026-01-23T17:21:21Z

Build successful! 🎉

rspbot · 2026-01-23T17:21:23Z

## API Changes

react-aria-components

/react-aria-components:DateSegmentRenderProps

 DateSegmentRenderProps {
   isDisabled: boolean
   isFocusVisible: boolean
   isFocused: boolean
   isHovered: boolean
   isInvalid: boolean
   isPlaceholder: boolean
   isReadOnly: boolean
   maxValue?: number
   minValue?: number
   placeholder: string
   text: string
   type: SegmentType
-  value?: number
+  value?: number | null
 }

/react-aria-components:DateFieldState

 DateFieldState {
   calendar: Calendar
   clearSegment: (SegmentType) => void
   commitValidation: () => void
   confirmPlaceholder: () => void
   dateFormatter: DateFormatter
   dateValue: Date
   decrement: (SegmentType) => void
   decrementPage: (SegmentType) => void
+  decrementToMin: (SegmentType) => void
   defaultValue: DateValue | null
   displayValidation: ValidationResult
   formatValue: (FieldOptions) => string
   getDateFormatter: (string, FormatterOptions) => DateFormatter
   granularity: Granularity
   increment: (SegmentType) => void
   incrementPage: (SegmentType) => void
+  incrementToMax: (SegmentType) => void
   isDisabled: boolean
   isInvalid: boolean
   isReadOnly: boolean
   isRequired: boolean
   realtimeValidation: ValidationResult
   resetValidation: () => void
   segments: Array<DateSegment>
   setSegment: (SegmentType, number) => void
   setValue: (DateValue | null) => void
   updateValidation: (ValidationResult) => void
   value: DateValue | null
 }

/react-aria-components:TimeFieldState

 TimeFieldState {
   calendar: Calendar
   clearSegment: (SegmentType) => void
   commitValidation: () => void
   confirmPlaceholder: () => void
   dateFormatter: DateFormatter
   dateValue: Date
   decrement: (SegmentType) => void
   decrementPage: (SegmentType) => void
+  decrementToMin: (SegmentType) => void
   defaultValue: DateValue | null
   displayValidation: ValidationResult
   formatValue: (FieldOptions) => string
   getDateFormatter: (string, FormatterOptions) => DateFormatter
   granularity: Granularity
   increment: (SegmentType) => void
   incrementPage: (SegmentType) => void
+  incrementToMax: (SegmentType) => void
   isDisabled: boolean
   isInvalid: boolean
   isReadOnly: boolean
   isRequired: boolean
   realtimeValidation: ValidationResult
   resetValidation: () => void
   segments: Array<DateSegment>
   setSegment: (SegmentType, number) => void
   setValue: (DateValue | null) => void
   timeValue: Time
   updateValidation: (ValidationResult) => void
   value: DateValue | null
 }

@internationalized/date

/@internationalized/date:Calendar

 Calendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getEras: () => Array<string>
   getFormattableMonth: (AnyCalendarDate) => CalendarDate
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMinimumDayInMonth: (AnyCalendarDate) => number
   getMinimumMonthInYear: (AnyCalendarDate) => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: (AnyCalendarDate) => number
   isEqual: (Calendar) => boolean
   toJulianDay: (AnyCalendarDate) => number
 }

/@internationalized/date:GregorianCalendar

 GregorianCalendar {
   balanceDate: (Mutable<AnyCalendarDate>) => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: (AnyCalendarDate) => number
   identifier: CalendarIdentifier
   isInverseEra: (AnyCalendarDate) => boolean
 }

/@internationalized/date:JapaneseCalendar

 JapaneseCalendar {
   balanceDate: (Mutable<AnyCalendarDate>) => void
   constrainDate: (Mutable<AnyCalendarDate>) => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMinimumDayInMonth: (AnyCalendarDate) => number
   getMinimumMonthInYear: (AnyCalendarDate) => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: (AnyCalendarDate) => number
   isInverseEra: (AnyCalendarDate) => boolean
   toJulianDay: (AnyCalendarDate) => number
 }

/@internationalized/date:BuddhistCalendar

 BuddhistCalendar {
   balanceDate: () => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: (AnyCalendarDate) => number
   identifier: CalendarIdentifier
   isInverseEra: (AnyCalendarDate) => boolean
 }

/@internationalized/date:TaiwanCalendar

 TaiwanCalendar {
   balanceDate: (Mutable<AnyCalendarDate>) => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: (AnyCalendarDate) => number
   identifier: CalendarIdentifier
   isInverseEra: (AnyCalendarDate) => boolean
 }

/@internationalized/date:PersianCalendar

 PersianCalendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:IndianCalendar

 IndianCalendar {
   balanceDate: () => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   isInverseEra: (AnyCalendarDate) => boolean
 }

/@internationalized/date:IslamicCivilCalendar

 IslamicCivilCalendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:IslamicTabularCalendar

 IslamicTabularCalendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:IslamicUmalquraCalendar

 IslamicUmalquraCalendar {
   constructor: () => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:HebrewCalendar

 HebrewCalendar {
   balanceYearMonth: (Mutable<AnyCalendarDate>, AnyCalendarDate) => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: (AnyCalendarDate) => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:EthiopicCalendar

 EthiopicCalendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: (AnyCalendarDate) => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:EthiopicAmeteAlemCalendar

 EthiopicAmeteAlemCalendar {
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: () => number
   identifier: CalendarIdentifier
   toJulianDay: (AnyCalendarDate) => number

/@internationalized/date:CopticCalendar

 CopticCalendar {
   balanceDate: (Mutable<AnyCalendarDate>) => void
   fromJulianDay: (number) => CalendarDate
   getDaysInMonth: (AnyCalendarDate) => number
   getDaysInYear: (AnyCalendarDate) => number
   getEras: () => Array<string>
+  getMaximumDaysInMonth: () => number
+  getMaximumMonthsInYear: () => number
   getMonthsInYear: () => number
   getYearsInEra: (AnyCalendarDate) => number
   identifier: CalendarIdentifier
   isInverseEra: (AnyCalendarDate) => boolean
 }

@react-stately/datepicker

/@react-stately/datepicker:DateFieldState

 DateFieldState {
   calendar: Calendar
   clearSegment: (SegmentType) => void
   commitValidation: () => void
   confirmPlaceholder: () => void
   dateFormatter: DateFormatter
   dateValue: Date
   decrement: (SegmentType) => void
   decrementPage: (SegmentType) => void
+  decrementToMin: (SegmentType) => void
   defaultValue: DateValue | null
   displayValidation: ValidationResult
   formatValue: (FieldOptions) => string
   getDateFormatter: (string, FormatterOptions) => DateFormatter
   granularity: Granularity
   increment: (SegmentType) => void
   incrementPage: (SegmentType) => void
+  incrementToMax: (SegmentType) => void
   isDisabled: boolean
   isInvalid: boolean
   isReadOnly: boolean
   isRequired: boolean
   realtimeValidation: ValidationResult
   resetValidation: () => void
   segments: Array<DateSegment>
   setSegment: (SegmentType, number) => void
   setValue: (DateValue | null) => void
   updateValidation: (ValidationResult) => void
   value: DateValue | null
 }

/@react-stately/datepicker:DateSegment

 DateSegment {
   isEditable: boolean
   isPlaceholder: boolean
   maxValue?: number
   minValue?: number
   placeholder: string
   text: string
   type: SegmentType
-  value?: number
+  value?: number | null
 }

/@react-stately/datepicker:TimeFieldState

 TimeFieldState {
   calendar: Calendar
   clearSegment: (SegmentType) => void
   commitValidation: () => void
   confirmPlaceholder: () => void
   dateFormatter: DateFormatter
   dateValue: Date
   decrement: (SegmentType) => void
   decrementPage: (SegmentType) => void
+  decrementToMin: (SegmentType) => void
   defaultValue: DateValue | null
   displayValidation: ValidationResult
   formatValue: (FieldOptions) => string
   getDateFormatter: (string, FormatterOptions) => DateFormatter
   granularity: Granularity
   increment: (SegmentType) => void
   incrementPage: (SegmentType) => void
+  incrementToMax: (SegmentType) => void
   isDisabled: boolean
   isInvalid: boolean
   isReadOnly: boolean
   isRequired: boolean
   realtimeValidation: ValidationResult
   resetValidation: () => void
   segments: Array<DateSegment>
   setSegment: (SegmentType, number) => void
   setValue: (DateValue | null) => void
   timeValue: Time
   updateValidation: (ValidationResult) => void
   value: DateValue | null
 }

devongovett · 2026-01-23T17:21:32Z

packages/@react-stately/datepicker/src/IncompleteDate.ts

+      case 'hour': {
+        // TODO: in the case of a "fall back" DST transition, the 1am hour repeats twice.
+        // With this logic, it's no longer possible to select the second instance.
+        // Using cycle from ZonedDateTime works as expected, but requires the date already be complete.


Repeating my previous comment since the code moved: Edge case! Previously you could enter 11/7/2021, 1:00 AM PST by first entering 11/7/2021, 1:00 AM PDT and then incrementing the hour field to switch from PDT to PST (try it here), but now that's impossible.

We could potentially check if the value is already complete (meaning we have all of the date fields and the hour), and in that case delegate to ZonedDateTime to handle the cycling. But it's impossible if we don't know the date yet – the user would need to enter everything and then go back and press the up arrow. Should we handle this case?

I probably can't quite test this the same way due to my locale/timezone, but for me, that link, if i press up on the hour cycle multiple times, it'll change like this and eventually move on:

I'm ok with not doing it, but if we get a bug report, I think we should be ready to patch it in some way or have a good reason we chose not to do it.

For instance, it could be more confusing that there are some cases we can figure out, but some that are impossible.

yes that's correct, that's the old behavior. but now it's not possible to enter the second time at all. incrementing from 1 goes to 2 without repeating.

LFDanLu

The logic looks good to me, seems to work well. The only other changed use case that I found was w/ regards to the Japanese calendar when set to the Heisei era (aka H) and navigating to the subsequent year via keyboard that should increment it to Reiwa (aka R).
The old behavior when you start at 30/12/28 and then increment the year up by one via ArrowUp is that it then changes to 1/12/28 (see the before and after screenshots)

However, now the current behavior for the same testing steps is that you hit 31/12/28 when pressing ArrowUp, upon which on blur will change to 31/4/28 aka the last day of the Heisei era.

Not sure this is a huge deal, but still digging to see why exactly this behavior changed

LFDanLu · 2026-01-28T23:08:59Z

packages/@react-stately/datepicker/src/useDateFieldState.ts

+  // use a NumberFormatter to manually format segments directly from raw numbers.
+  // When the user blurs the date field, the invalid segments will be constrained.
+  let numberFormatter = new NumberFormatter(locale, {useGrouping: false});
+  let twoDigitFormatter = new NumberFormatter(locale, {useGrouping: false, minimumIntegerDigits: 2});


now that we use NumberFormatter for the segments, we could theoretically support leading zeros for the year segment right? I don't think it is very necessary persay (not sure how common people typing leading zeros for years would be) but it would bring the year segment in line with the month and days for shouldForceLeadingZeros

I think it's uncommon to force leading zeroes for years, but I don't know about other locales/calendars

LFDanLu · 2026-01-28T23:23:33Z

packages/@react-stately/datepicker/src/IncompleteDate.ts

+        // Use CalendarDate to cycle so that we update the era when going between 1 AD and 1 BC.
+        let date = new CalendarDate(this.calendar, this.era ?? placeholder.era, this.year ?? placeholder.year, 1, 1);
+        date = date.cycle(field, amount, {round: field === 'year'});
+        res.era = date.era;
+        res.year = date.year;


oh actually is this why the era handling for the japanese eras changed (and perhaps other calendar dates that had eras)? Would we need to special case those as well?

oh I guess it's because we're hard coding the month and day to 1 here, but the Reiwa era began on May 1st so R 1/1/1 never existed. We could use the actual values but only if they have already been entered - if only the year/era have been entered we'd still get this behavior. Similar problem to the timezone issue I mentioned above. So we have to decide between cycling behaving consistently independent from other fields, or sometimes depending on entering other fields first.

devongovett · 2026-01-29T01:51:42Z

Gonna merge this and we can decide how we want to handle the edge cases after.

see #9510 (review) and #9510 (review)

feat: Support entering invalid dates in DateField and constrain on blur

c004da5

devongovett commented Jan 22, 2026

View reviewed changes

Fix crash when switching calendar systems

d97486a

snowystinger reviewed Jan 22, 2026

View reviewed changes

Refactor to support entering leading zeros

bcb86f6

devongovett commented Jan 23, 2026

View reviewed changes

devongovett added release ready for review labels Jan 27, 2026

snowystinger approved these changes Jan 28, 2026

View reviewed changes

LFDanLu approved these changes Jan 28, 2026

View reviewed changes

LFDanLu reviewed Jan 28, 2026

View reviewed changes

devongovett added this pull request to the merge queue Jan 29, 2026

Merged via the queue into main with commit 1d16513 Jan 29, 2026
34 checks passed

devongovett deleted the datefield-incomplete branch January 29, 2026 02:01

LFDanLu added a commit that referenced this pull request Jan 30, 2026

fix: handle japanese era and daylight savings transitions

4e9b132

see #9510 (review) and #9510 (review)

LFDanLu mentioned this pull request Jan 30, 2026

fix: DateField keyboard cycling doesnt skip datetimes across era and daylight saving boundaries #9561

Open

5 tasks

yihuiliao added DateField RAC and removed RAC labels Jan 30, 2026

feat: Support entering invalid dates in DateField and constrain on blur #9510

feat: Support entering invalid dates in DateField and constrain on blur #9510

Conversation

devongovett commented Jan 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rspbot commented Jan 22, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

snowystinger left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

devongovett commented Jan 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rspbot commented Jan 23, 2026

Uh oh!

rspbot commented Jan 23, 2026

react-aria-components

/react-aria-components:DateSegmentRenderProps

/react-aria-components:DateFieldState

/react-aria-components:TimeFieldState

@internationalized/date

/@internationalized/date:Calendar

/@internationalized/date:GregorianCalendar

/@internationalized/date:JapaneseCalendar

/@internationalized/date:BuddhistCalendar

/@internationalized/date:TaiwanCalendar

/@internationalized/date:PersianCalendar

/@internationalized/date:IndianCalendar

/@internationalized/date:IslamicCivilCalendar

/@internationalized/date:IslamicTabularCalendar

/@internationalized/date:IslamicUmalquraCalendar

/@internationalized/date:HebrewCalendar

/@internationalized/date:EthiopicCalendar

/@internationalized/date:EthiopicAmeteAlemCalendar

/@internationalized/date:CopticCalendar

@react-stately/datepicker

/@react-stately/datepicker:DateFieldState

/@react-stately/datepicker:DateSegment

/@react-stately/datepicker:TimeFieldState

Uh oh!

Choose a reason for hiding this comment

Uh oh!

snowystinger Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

LFDanLu left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

devongovett commented Jan 29, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

devongovett commented Jan 22, 2026 •

edited

Loading

snowystinger left a comment •

edited

Loading

snowystinger Jan 28, 2026 •

edited

Loading