You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using useDatePicker from React Aria in our forms, but we now have a requirement to allow users to select a quarter (Q1–Q4) rather than a specific date.
From reviewing the existing date APIs, it appears that the current abstractions are centered around day-level selection. While it may be possible to approximate quarter selection using lower-level primitives like useCalendar, it doesn’t seem to map cleanly to the interaction model of a typical quarter picker.
A quarter picker differs in a few ways:
The selection unit is a quarter, not a day.
The UI typically presents four selectable options per year.
The value represents a logical quarter (or quarter range) rather than a single date.
Accessibility semantics and keyboard behavior would likely differ from a traditional date grid.
Is quarter-level selection considered in scope for React Aria / React Spectrum date components?
If not currently supported, would it make sense to introduce first-class support for quarter selection — either via an extension of the existing date picker abstractions or a dedicated hook/component?
This is a fairly common requirement in enterprise reporting workflows, and having an accessible, internationalized primitive for it would be valuable.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We are currently using
useDatePickerfrom React Aria in our forms, but we now have a requirement to allow users to select a quarter (Q1–Q4) rather than a specific date.From reviewing the existing date APIs, it appears that the current abstractions are centered around day-level selection. While it may be possible to approximate quarter selection using lower-level primitives like useCalendar, it doesn’t seem to map cleanly to the interaction model of a typical quarter picker.
A quarter picker differs in a few ways:
Is quarter-level selection considered in scope for React Aria / React Spectrum date components?
If not currently supported, would it make sense to introduce first-class support for quarter selection — either via an extension of the existing date picker abstractions or a dedicated hook/component?
This is a fairly common requirement in enterprise reporting workflows, and having an accessible, internationalized primitive for it would be valuable.
Beta Was this translation helpful? Give feedback.
All reactions