DateRangePicker
A date range picker combines two DateFields and a RangeCalendar popover to allow users to enter or select a date and time range.
install | yarn add react-aria-components |
---|---|
version | 1.0.0-beta.1 |
usage | import {DateRangePicker} from 'react-aria-components' |
Example#
import {Button, CalendarCell, CalendarGrid, DateInput, DateRangePicker, DateSegment, Dialog, Group, Heading, Label, Popover, RangeCalendar} from 'react-aria-components';
<DateRangePicker>
<Label>Trip dates</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {
Button,
CalendarCell,
CalendarGrid,
DateInput,
DateRangePicker,
DateSegment,
Dialog,
Group,
Heading,
Label,
Popover,
RangeCalendar
} from 'react-aria-components';
<DateRangePicker>
<Label>Trip dates</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {
Button,
CalendarCell,
CalendarGrid,
DateInput,
DateRangePicker,
DateSegment,
Dialog,
Group,
Heading,
Label,
Popover,
RangeCalendar
} from 'react-aria-components';
<DateRangePicker>
<Label>
Trip dates
</Label>
<Group>
<DateInput slot="start">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<span aria-hidden="true">
–
</span>
<DateInput slot="end">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">
◀
</Button>
<Heading />
<Button slot="next">
▶
</Button>
</header>
<CalendarGrid>
{(date) => (
<CalendarCell
date={date}
/>
)}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
Show CSS
.react-aria-DateRangePicker {
--field-border: var(--spectrum-global-color-gray-400);
--field-background: var(--spectrum-global-color-gray-50);
--text-color: var(--spectrum-alias-text-color);
--text-color-placeholder: var(--spectrum-global-color-gray-700);
--text-color-invalid: var(--spectrum-global-color-red-600);
--highlight-background: slateblue;
--highlight-foreground: white;
--highlight-background-invalid: var(--spectrum-global-color-static-red-600);
color: var(--text-color);
.react-aria-Group {
display: flex;
align-items: center;
width: fit-content;
min-width: 220px;
max-width: 100%;
box-sizing: border-box;
overflow: auto;
position: relative;
padding: 2px 2px 2px 8px;
border: 1px solid var(--field-border);
border-radius: 6px;
background: var(--field-background);
white-space: nowrap;
&[data-focus-within] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
}
[slot=start] + span {
padding: 0 4px;
}
[slot=end] {
margin-right: 2rem;
flex: 1;
}
.react-aria-Button {
background: slateblue;
color: white;
border-radius: 4px;
border: none;
appearance: none;
margin-left: auto;
width: 1.429rem;
height: 1.429rem;
padding: 0;
vertical-align: middle;
font-size: 0.857rem;
outline: none;
box-sizing: content-box;
flex-shrink: 0;
border: 2px solid var(--page-background);
position: sticky;
right: 0;
&[data-focus-visible] {
box-shadow: 0 0 0 2px slateblue;
}
}
[slot=description] {
font-size: 12px;
}
[slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
&[data-invalid] {
[slot=end]:after {
content: '🚫' / '';
content: '🚫';
alt: ' ';
flex: 1;
text-align: end;
margin-right: -2rem;
}
}
}
.react-aria-DateInput {
display: flex;
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--text-color-placeholder);
font-style: italic;
}
&:focus {
color: var(--highlight-foreground);
background: var(--highlight-background);
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[data-invalid] {
color: var(--text-color-invalid);
&:focus {
background: var(--highlight-background-invalid);
color: var(--highlight-foreground);
}
}
}
.react-aria-RangeCalendar {
--highlight-background: slateblue;
--highlight-foreground: white;
--button-background: var(--spectrum-global-color-gray-50);
--button-background-pressed: var(--spectrum-global-color-gray-100);
--button-border: var(--spectrum-global-color-gray-400);
--text-color: var(--spectrum-alias-text-color);
--text-color-disabled: var(--spectrum-alias-text-color-disabled);
--text-color-invalid: var(--spectrum-global-color-red-600);
--pressed-color: var(--spectrum-global-color-gray-200);
--unavailable-color: var(--spectrum-global-color-red-600);
--invalid-color: var(--spectrum-global-color-static-red-600);
width: fit-content;
color: var(--text-color);
& header {
display: flex;
align-items: center;
margin: 0 4px .5rem 4px;
.react-aria-Heading {
flex: 1;
margin: 0;
text-align: center;
font-size: 1.375rem;
}
.react-aria-Button {
background: var(--button-background);
border: 1px solid var(--button-border);
color: var(--text-color);
box-shadow: 0 1px 2px rgba(0 0 0 / 0.1);
border-radius: 4px;
appearance: none;
vertical-align: middle;
font-size: 1rem;
width: 2rem;
height: 2rem;
padding: 0;
text-align: center;
margin: 0;
outline: none;
&[data-focus-visible] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
&[data-pressed] {
background: var(--button-background-pressed);
}
}
}
& table {
border-collapse: collapse;
& td {
padding: 2px 0;
}
}
.react-aria-CalendarCell {
width: 2.286rem;
line-height: 2.286rem;
text-align: center;
border-radius: 6px;
cursor: default;
outline: none;
&[data-outside-month] {
display: none;
}
&[data-pressed] {
background: var(--pressed-color);
}
&[data-focus-visible] {
box-shadow: inset 0 0 0 2px var(--highlight-background);
}
&[data-selected] {
background: var(--highlight-background);
color: var(--highlight-foreground);
border-radius: 0;
&[data-focus-visible] {
box-shadow: inset 0 0 0 1px var(--highlight-background), inset 0 0 0 3px var(--highlight-foreground);
}
}
&[data-selection-start] {
border-start-start-radius: 6px;
border-end-start-radius: 6px;
}
&[data-selection-end] {
border-start-end-radius: 6px;
border-end-end-radius: 6px;
}
&[data-disabled] {
color: var(--text-color-disabled);
}
&[data-unavailable] {
text-decoration: line-through;
color: var(--unavailable-color);
}
&[data-invalid] {
background: var(--invalid-color);
color: var(--highlight-foreground);
}
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
}
.react-aria-Popover {
overflow: auto;
border: 1px solid var(--spectrum-global-color-gray-400);
box-shadow: 0 8px 20px rgba(0 0 0 / 0.1);
border-radius: 6px;
background: var(--page-background);
padding: 1.25rem;
&[data-placement=top] {
--origin: translateY(8px);
}
&[data-placement=bottom] {
--origin: translateY(-8px);
}
&[data-entering] {
animation: slide 200ms;
}
&[data-exiting] {
animation: slide 200ms reverse ease-in;
}
}
@keyframes slide {
from {
transform: var(--origin);
opacity: 0;
}
to {
transform: translateY(0);
opacity: 1;
}
}
@media (forced-colors: active) {
.react-aria-DateRangePicker {
forced-color-adjust: none;
--field-border: ButtonBorder;
--field-background: Field;
--text-color: FieldText;
--text-color-placeholder: FieldText;
--text-color-invalid: LinkText;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--highlight-background-invalid: LinkText;
.react-aria-Button {
forced-color-adjust: none;
--focus-ring-color: Highlight;
background: ButtonFace;
color: ButtonText;
border: 1px solid ButtonBorder;
&[data-focus-visible] {
border-color: Highlight;
box-shadow: 0 0 0 1px Highlight;
}
}
}
.react-aria-RangeCalendar {
forced-color-adjust: none;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--button-border: ButtonBorder;
--button-border-disabled: GrayText;
--button-background: ButtonFace;
--text-color: ButtonText;
--text-color-disabled: GrayText;
--text-color-invalid: LinkText;
--unavailable-color: GrayText;
--invalid-color: LinkText;
--pressed-color: Canvas;
--spectrum-alias-background-color-default: Canvas;
}
}
.react-aria-DateRangePicker {
--field-border: var(--spectrum-global-color-gray-400);
--field-background: var(--spectrum-global-color-gray-50);
--text-color: var(--spectrum-alias-text-color);
--text-color-placeholder: var(--spectrum-global-color-gray-700);
--text-color-invalid: var(--spectrum-global-color-red-600);
--highlight-background: slateblue;
--highlight-foreground: white;
--highlight-background-invalid: var(--spectrum-global-color-static-red-600);
color: var(--text-color);
.react-aria-Group {
display: flex;
align-items: center;
width: fit-content;
min-width: 220px;
max-width: 100%;
box-sizing: border-box;
overflow: auto;
position: relative;
padding: 2px 2px 2px 8px;
border: 1px solid var(--field-border);
border-radius: 6px;
background: var(--field-background);
white-space: nowrap;
&[data-focus-within] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
}
[slot=start] + span {
padding: 0 4px;
}
[slot=end] {
margin-right: 2rem;
flex: 1;
}
.react-aria-Button {
background: slateblue;
color: white;
border-radius: 4px;
border: none;
appearance: none;
margin-left: auto;
width: 1.429rem;
height: 1.429rem;
padding: 0;
vertical-align: middle;
font-size: 0.857rem;
outline: none;
box-sizing: content-box;
flex-shrink: 0;
border: 2px solid var(--page-background);
position: sticky;
right: 0;
&[data-focus-visible] {
box-shadow: 0 0 0 2px slateblue;
}
}
[slot=description] {
font-size: 12px;
}
[slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
&[data-invalid] {
[slot=end]:after {
content: '🚫' / '';
content: '🚫';
alt: ' ';
flex: 1;
text-align: end;
margin-right: -2rem;
}
}
}
.react-aria-DateInput {
display: flex;
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--text-color-placeholder);
font-style: italic;
}
&:focus {
color: var(--highlight-foreground);
background: var(--highlight-background);
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[data-invalid] {
color: var(--text-color-invalid);
&:focus {
background: var(--highlight-background-invalid);
color: var(--highlight-foreground);
}
}
}
.react-aria-RangeCalendar {
--highlight-background: slateblue;
--highlight-foreground: white;
--button-background: var(--spectrum-global-color-gray-50);
--button-background-pressed: var(--spectrum-global-color-gray-100);
--button-border: var(--spectrum-global-color-gray-400);
--text-color: var(--spectrum-alias-text-color);
--text-color-disabled: var(--spectrum-alias-text-color-disabled);
--text-color-invalid: var(--spectrum-global-color-red-600);
--pressed-color: var(--spectrum-global-color-gray-200);
--unavailable-color: var(--spectrum-global-color-red-600);
--invalid-color: var(--spectrum-global-color-static-red-600);
width: fit-content;
color: var(--text-color);
& header {
display: flex;
align-items: center;
margin: 0 4px .5rem 4px;
.react-aria-Heading {
flex: 1;
margin: 0;
text-align: center;
font-size: 1.375rem;
}
.react-aria-Button {
background: var(--button-background);
border: 1px solid var(--button-border);
color: var(--text-color);
box-shadow: 0 1px 2px rgba(0 0 0 / 0.1);
border-radius: 4px;
appearance: none;
vertical-align: middle;
font-size: 1rem;
width: 2rem;
height: 2rem;
padding: 0;
text-align: center;
margin: 0;
outline: none;
&[data-focus-visible] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
&[data-pressed] {
background: var(--button-background-pressed);
}
}
}
& table {
border-collapse: collapse;
& td {
padding: 2px 0;
}
}
.react-aria-CalendarCell {
width: 2.286rem;
line-height: 2.286rem;
text-align: center;
border-radius: 6px;
cursor: default;
outline: none;
&[data-outside-month] {
display: none;
}
&[data-pressed] {
background: var(--pressed-color);
}
&[data-focus-visible] {
box-shadow: inset 0 0 0 2px var(--highlight-background);
}
&[data-selected] {
background: var(--highlight-background);
color: var(--highlight-foreground);
border-radius: 0;
&[data-focus-visible] {
box-shadow: inset 0 0 0 1px var(--highlight-background), inset 0 0 0 3px var(--highlight-foreground);
}
}
&[data-selection-start] {
border-start-start-radius: 6px;
border-end-start-radius: 6px;
}
&[data-selection-end] {
border-start-end-radius: 6px;
border-end-end-radius: 6px;
}
&[data-disabled] {
color: var(--text-color-disabled);
}
&[data-unavailable] {
text-decoration: line-through;
color: var(--unavailable-color);
}
&[data-invalid] {
background: var(--invalid-color);
color: var(--highlight-foreground);
}
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
}
.react-aria-Popover {
overflow: auto;
border: 1px solid var(--spectrum-global-color-gray-400);
box-shadow: 0 8px 20px rgba(0 0 0 / 0.1);
border-radius: 6px;
background: var(--page-background);
padding: 1.25rem;
&[data-placement=top] {
--origin: translateY(8px);
}
&[data-placement=bottom] {
--origin: translateY(-8px);
}
&[data-entering] {
animation: slide 200ms;
}
&[data-exiting] {
animation: slide 200ms reverse ease-in;
}
}
@keyframes slide {
from {
transform: var(--origin);
opacity: 0;
}
to {
transform: translateY(0);
opacity: 1;
}
}
@media (forced-colors: active) {
.react-aria-DateRangePicker {
forced-color-adjust: none;
--field-border: ButtonBorder;
--field-background: Field;
--text-color: FieldText;
--text-color-placeholder: FieldText;
--text-color-invalid: LinkText;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--highlight-background-invalid: LinkText;
.react-aria-Button {
forced-color-adjust: none;
--focus-ring-color: Highlight;
background: ButtonFace;
color: ButtonText;
border: 1px solid ButtonBorder;
&[data-focus-visible] {
border-color: Highlight;
box-shadow: 0 0 0 1px Highlight;
}
}
}
.react-aria-RangeCalendar {
forced-color-adjust: none;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--button-border: ButtonBorder;
--button-border-disabled: GrayText;
--button-background: ButtonFace;
--text-color: ButtonText;
--text-color-disabled: GrayText;
--text-color-invalid: LinkText;
--unavailable-color: GrayText;
--invalid-color: LinkText;
--pressed-color: Canvas;
--spectrum-alias-background-color-default: Canvas;
}
}
.react-aria-DateRangePicker {
--field-border: var(--spectrum-global-color-gray-400);
--field-background: var(--spectrum-global-color-gray-50);
--text-color: var(--spectrum-alias-text-color);
--text-color-placeholder: var(--spectrum-global-color-gray-700);
--text-color-invalid: var(--spectrum-global-color-red-600);
--highlight-background: slateblue;
--highlight-foreground: white;
--highlight-background-invalid: var(--spectrum-global-color-static-red-600);
color: var(--text-color);
.react-aria-Group {
display: flex;
align-items: center;
width: fit-content;
min-width: 220px;
max-width: 100%;
box-sizing: border-box;
overflow: auto;
position: relative;
padding: 2px 2px 2px 8px;
border: 1px solid var(--field-border);
border-radius: 6px;
background: var(--field-background);
white-space: nowrap;
&[data-focus-within] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
}
[slot=start] + span {
padding: 0 4px;
}
[slot=end] {
margin-right: 2rem;
flex: 1;
}
.react-aria-Button {
background: slateblue;
color: white;
border-radius: 4px;
border: none;
appearance: none;
margin-left: auto;
width: 1.429rem;
height: 1.429rem;
padding: 0;
vertical-align: middle;
font-size: 0.857rem;
outline: none;
box-sizing: content-box;
flex-shrink: 0;
border: 2px solid var(--page-background);
position: sticky;
right: 0;
&[data-focus-visible] {
box-shadow: 0 0 0 2px slateblue;
}
}
[slot=description] {
font-size: 12px;
}
[slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
&[data-invalid] {
[slot=end]:after {
content: '🚫' / '';
content: '🚫';
alt: ' ';
flex: 1;
text-align: end;
margin-right: -2rem;
}
}
}
.react-aria-DateInput {
display: flex;
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--text-color-placeholder);
font-style: italic;
}
&:focus {
color: var(--highlight-foreground);
background: var(--highlight-background);
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[data-invalid] {
color: var(--text-color-invalid);
&:focus {
background: var(--highlight-background-invalid);
color: var(--highlight-foreground);
}
}
}
.react-aria-RangeCalendar {
--highlight-background: slateblue;
--highlight-foreground: white;
--button-background: var(--spectrum-global-color-gray-50);
--button-background-pressed: var(--spectrum-global-color-gray-100);
--button-border: var(--spectrum-global-color-gray-400);
--text-color: var(--spectrum-alias-text-color);
--text-color-disabled: var(--spectrum-alias-text-color-disabled);
--text-color-invalid: var(--spectrum-global-color-red-600);
--pressed-color: var(--spectrum-global-color-gray-200);
--unavailable-color: var(--spectrum-global-color-red-600);
--invalid-color: var(--spectrum-global-color-static-red-600);
width: fit-content;
color: var(--text-color);
& header {
display: flex;
align-items: center;
margin: 0 4px .5rem 4px;
.react-aria-Heading {
flex: 1;
margin: 0;
text-align: center;
font-size: 1.375rem;
}
.react-aria-Button {
background: var(--button-background);
border: 1px solid var(--button-border);
color: var(--text-color);
box-shadow: 0 1px 2px rgba(0 0 0 / 0.1);
border-radius: 4px;
appearance: none;
vertical-align: middle;
font-size: 1rem;
width: 2rem;
height: 2rem;
padding: 0;
text-align: center;
margin: 0;
outline: none;
&[data-focus-visible] {
border-color: var(--highlight-background);
box-shadow: 0 0 0 1px var(--highlight-background);
}
&[data-pressed] {
background: var(--button-background-pressed);
}
}
}
& table {
border-collapse: collapse;
& td {
padding: 2px 0;
}
}
.react-aria-CalendarCell {
width: 2.286rem;
line-height: 2.286rem;
text-align: center;
border-radius: 6px;
cursor: default;
outline: none;
&[data-outside-month] {
display: none;
}
&[data-pressed] {
background: var(--pressed-color);
}
&[data-focus-visible] {
box-shadow: inset 0 0 0 2px var(--highlight-background);
}
&[data-selected] {
background: var(--highlight-background);
color: var(--highlight-foreground);
border-radius: 0;
&[data-focus-visible] {
box-shadow: inset 0 0 0 1px var(--highlight-background), inset 0 0 0 3px var(--highlight-foreground);
}
}
&[data-selection-start] {
border-start-start-radius: 6px;
border-end-start-radius: 6px;
}
&[data-selection-end] {
border-start-end-radius: 6px;
border-end-end-radius: 6px;
}
&[data-disabled] {
color: var(--text-color-disabled);
}
&[data-unavailable] {
text-decoration: line-through;
color: var(--unavailable-color);
}
&[data-invalid] {
background: var(--invalid-color);
color: var(--highlight-foreground);
}
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--text-color-invalid);
}
}
.react-aria-Popover {
overflow: auto;
border: 1px solid var(--spectrum-global-color-gray-400);
box-shadow: 0 8px 20px rgba(0 0 0 / 0.1);
border-radius: 6px;
background: var(--page-background);
padding: 1.25rem;
&[data-placement=top] {
--origin: translateY(8px);
}
&[data-placement=bottom] {
--origin: translateY(-8px);
}
&[data-entering] {
animation: slide 200ms;
}
&[data-exiting] {
animation: slide 200ms reverse ease-in;
}
}
@keyframes slide {
from {
transform: var(--origin);
opacity: 0;
}
to {
transform: translateY(0);
opacity: 1;
}
}
@media (forced-colors: active) {
.react-aria-DateRangePicker {
forced-color-adjust: none;
--field-border: ButtonBorder;
--field-background: Field;
--text-color: FieldText;
--text-color-placeholder: FieldText;
--text-color-invalid: LinkText;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--highlight-background-invalid: LinkText;
.react-aria-Button {
forced-color-adjust: none;
--focus-ring-color: Highlight;
background: ButtonFace;
color: ButtonText;
border: 1px solid ButtonBorder;
&[data-focus-visible] {
border-color: Highlight;
box-shadow: 0 0 0 1px Highlight;
}
}
}
.react-aria-RangeCalendar {
forced-color-adjust: none;
--highlight-background: Highlight;
--highlight-foreground: HighlightText;
--button-border: ButtonBorder;
--button-border-disabled: GrayText;
--button-background: ButtonFace;
--text-color: ButtonText;
--text-color-disabled: GrayText;
--text-color-invalid: LinkText;
--unavailable-color: GrayText;
--invalid-color: LinkText;
--pressed-color: Canvas;
--spectrum-alias-background-color-default: Canvas;
}
}
Features#
A date range picker can be built using two separate <input type="date">
elements, but this is very limited in functionality, lacking in internationalization capabilities, inconsistent between browsers, and difficult to style. DateRangePicker
helps achieve accessible and international date and time range pickers that can be styled as needed.
- Dates and times – Support for dates and times with configurable granularity.
- International – Support for 13 calendar systems used around the world, including Gregorian, Buddhist, Islamic, Persian, and more. Locale-specific formatting, number systems, hour cycles, and right-to-left support are available as well.
- Time zone aware – Dates and times can optionally include a time zone. All modifications follow time zone rules such as daylight saving time.
- Accessible – Each date and time unit is displayed as an individually focusable and editable segment, which allows users an easy way to edit dates using the keyboard, in any date format and locale. Users can also open a calendar popover to select date ranges in a standard month grid. Localized screen reader messages are included to announce when the selection and visible date range change.
- Touch friendly – Date segments are editable using an easy to use numeric keypad, date ranges can be selected by dragging over dates in the calendar using a touch screen, and all interactions are accessible using touch-based screen readers.
- Customizable – As with all of React Aria, the DOM structure and styling of all elements can be fully customized.
Read our blog post for more details about the internationalization, accessibility, and user experience features implemented by DateRangePicker
.
Anatomy#
A date range picker consists of a label, and group containing two date fields and a button. Clicking the button opens a popup containing a range calendar. The date fields include segments representing each unit of a date and time (e.g. years, months, days, etc.), each of which is individually focusable and editable using the keyboard. The calendar popup offers a more visual way of choosing a date range.
DateRangePicker
also supports optional description and error message elements, which can be used to provide more context about the field, and any validation messages. These are linked with the input via the aria-describedby
attribute.
import {Button, CalendarCell, CalendarGrid, CalendarGridBody, CalendarGridHeader, CalendarHeaderCell, DateInput, DateRangePicker, DateSegment, Dialog, Group, Heading, Label, Popover, RangeCalendar, Text} from 'react-aria-components';
<DateRangePicker>
<Label />
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button />
</Group>
<Text slot="description" />
<Text slot="errorMessage" />
<Popover>
<Dialog>
<RangeCalendar>
<Button slot="previous" />
<Heading />
<Button slot="next" />
<CalendarGrid>
<CalendarGridHeader>
{(day) => <CalendarHeaderCell />}
</CalendarGridHeader>
<CalendarGridBody>
{(date) => <CalendarCell date={date} />}
</CalendarGridBody>
</CalendarGrid>
<Text slot="errorMessage" />
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {
Button,
CalendarCell,
CalendarGrid,
CalendarGridBody,
CalendarGridHeader,
CalendarHeaderCell,
DateInput,
DateRangePicker,
DateSegment,
Dialog,
Group,
Heading,
Label,
Popover,
RangeCalendar,
Text
} from 'react-aria-components';
<DateRangePicker>
<Label />
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button />
</Group>
<Text slot="description" />
<Text slot="errorMessage" />
<Popover>
<Dialog>
<RangeCalendar>
<Button slot="previous" />
<Heading />
<Button slot="next" />
<CalendarGrid>
<CalendarGridHeader>
{(day) => <CalendarHeaderCell />}
</CalendarGridHeader>
<CalendarGridBody>
{(date) => <CalendarCell date={date} />}
</CalendarGridBody>
</CalendarGrid>
<Text slot="errorMessage" />
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {
Button,
CalendarCell,
CalendarGrid,
CalendarGridBody,
CalendarGridHeader,
CalendarHeaderCell,
DateInput,
DateRangePicker,
DateSegment,
Dialog,
Group,
Heading,
Label,
Popover,
RangeCalendar,
Text
} from 'react-aria-components';
<DateRangePicker>
<Label />
<Group>
<DateInput slot="start">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<DateInput slot="end">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<Button />
</Group>
<Text slot="description" />
<Text slot="errorMessage" />
<Popover>
<Dialog>
<RangeCalendar>
<Button slot="previous" />
<Heading />
<Button slot="next" />
<CalendarGrid>
<CalendarGridHeader>
{(day) => (
<CalendarHeaderCell />
)}
</CalendarGridHeader>
<CalendarGridBody>
{(date) => (
<CalendarCell
date={date}
/>
)}
</CalendarGridBody>
</CalendarGrid>
<Text slot="errorMessage" />
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
If the date range picker does not have a visible label, an aria-label
or aria-labelledby
prop must be passed instead to identify it to assistive technology.
Note that most of this anatomy is shared with DatePicker, so you can reuse many components between them if you have both.
Concepts#
DateRangePicker
makes use of the following concepts:
Composed components#
A DateRangePicker
uses the following components, which may also be used standalone or reused in other components.
Reusable wrappers#
If you will use a DateRangePicker in multiple places in your app, you can wrap all of the pieces into a reusable component. This way, the DOM structure, styling code, and other logic are defined in a single place and reused everywhere to ensure consistency.
This example wraps DateRangePicker
and all of its children together into a single component which accepts a label
prop, which is passed to the right place. It also shows how to use the description
and errorMessage
slots to render help text (see below for details).
import type {DateRangePickerProps, DateValue} from 'react-aria-components';
import {Text} from 'react-aria-components';
interface MyDateRangePickerProps<T extends DateValue>
extends DateRangePickerProps<T> {
label?: string;
description?: string;
errorMessage?: string;
}
function MyDateRangePicker<T extends DateValue>(
{ label, description, errorMessage, ...props }: MyDateRangePickerProps<T>
) {
return (
<DateRangePicker {...props}>
<Label>{label}</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button>▼</Button>
</Group>
{description && <Text slot="description">{description}</Text>}
{errorMessage && <Text slot="errorMessage">{errorMessage}</Text>}
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
{errorMessage && <Text slot="errorMessage">{errorMessage}</Text>}
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
);
}
<MyDateRangePicker label="Event date" />
import type {
DateRangePickerProps,
DateValue
} from 'react-aria-components';
import {Text} from 'react-aria-components';
interface MyDateRangePickerProps<T extends DateValue>
extends DateRangePickerProps<T> {
label?: string;
description?: string;
errorMessage?: string;
}
function MyDateRangePicker<T extends DateValue>(
{ label, description, errorMessage, ...props }:
MyDateRangePickerProps<T>
) {
return (
<DateRangePicker {...props}>
<Label>{label}</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<Button>▼</Button>
</Group>
{description && (
<Text slot="description">{description}</Text>
)}
{errorMessage && (
<Text slot="errorMessage">{errorMessage}</Text>
)}
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
{errorMessage && (
<Text slot="errorMessage">
{errorMessage}
</Text>
)}
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
);
}
<MyDateRangePicker label="Event date" />
import type {
DateRangePickerProps,
DateValue
} from 'react-aria-components';
import {Text} from 'react-aria-components';
interface MyDateRangePickerProps<
T extends DateValue
> extends
DateRangePickerProps<
T
> {
label?: string;
description?: string;
errorMessage?: string;
}
function MyDateRangePicker<
T extends DateValue
>(
{
label,
description,
errorMessage,
...props
}: MyDateRangePickerProps<
T
>
) {
return (
<DateRangePicker
{...props}
>
<Label>
{label}
</Label>
<Group>
<DateInput slot="start">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<span aria-hidden="true">
–
</span>
<DateInput slot="end">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<Button>
▼
</Button>
</Group>
{description && (
<Text slot="description">
{description}
</Text>
)}
{errorMessage && (
<Text slot="errorMessage">
{errorMessage}
</Text>
)}
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">
◀
</Button>
<Heading />
<Button slot="next">
▶
</Button>
</header>
<CalendarGrid>
{(date) => (
<CalendarCell
date={date}
/>
)}
</CalendarGrid>
{errorMessage &&
(
<Text slot="errorMessage">
{errorMessage}
</Text>
)}
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
);
}
<MyDateRangePicker label="Event date" />
Value#
A DateRangePicker
displays a placeholder by default. An initial, uncontrolled value can be provided to the DateRangePicker
using the defaultValue
prop. Alternatively, a controlled value can be provided using the value
prop.
Date ranges are objects with start
and end
properties containing date values, which are provided using objects in the @internationalized/date package. This library handles correct international date manipulation across calendars, time zones, and other localization concerns. DateRangePicker
supports values of the following types:
CalendarDate
– a date without any time components. May be parsed from a string representation using theparseDate
function. Use this type to represent dates where the time is not important, such as a birthday or an all day calendar event.CalendarDateTime
– a date with a time, but not in any specific time zone. May be parsed from a string representation using theparseDateTime
function. Use this type to represent times that occur at the same local time regardless of the time zone, such as the time of New Years Eve fireworks which always occur at midnight. Most times are better stored as aZonedDateTime
.ZonedDateTime
– a date with a time in a specific time zone. May be parsed from a string representation using theparseZonedDateTime
,parseAbsolute
, orparseAbsoluteToLocal
functions. Use this type to represent an exact moment in time at a particular location on Earth.
import {parseDate} from '@internationalized/date';
function Example() {
let [value, setValue] = React.useState({
start: parseDate('2020-02-03'),
end: parseDate('2020-02-08')
});
return (
<>
<MyDateRangePicker
label="Date range (uncontrolled)"
defaultValue={{
start: parseDate('2020-02-03'),
end: parseDate('2020-02-08')
}} />
<MyDateRangePicker
label="Date range (controlled)"
value={value}
onChange={setValue} />
</>
);
}
import {parseDate} from '@internationalized/date';
function Example() {
let [value, setValue] = React.useState({
start: parseDate('2020-02-03'),
end: parseDate('2020-02-08')
});
return (
<>
<MyDateRangePicker
label="Date range (uncontrolled)"
defaultValue={{
start: parseDate('2020-02-03'),
end: parseDate('2020-02-08')
}} />
<MyDateRangePicker
label="Date range (controlled)"
value={value}
onChange={setValue} />
</>
);
}
import {parseDate} from '@internationalized/date';
function Example() {
let [value, setValue] =
React.useState({
start: parseDate(
'2020-02-03'
),
end: parseDate(
'2020-02-08'
)
});
return (
<>
<MyDateRangePicker
label="Date range (uncontrolled)"
defaultValue={{
start:
parseDate(
'2020-02-03'
),
end: parseDate(
'2020-02-08'
)
}}
/>
<MyDateRangePicker
label="Date range (controlled)"
value={value}
onChange={setValue}
/>
</>
);
}
Time zones#
DateRangePicker
is time zone aware when ZonedDateTime
objects are provided as the value. In this case, the time zone abbreviation is displayed, and time zone concerns such as daylight saving time are taken into account when the value is manipulated.
In most cases, your data will come from and be sent to a server as an ISO 8601 formatted string. @internationalized/date includes functions for parsing strings in multiple formats into ZonedDateTime
objects. Which format you use will depend on what information you need to store.
parseZonedDateTime
– This function parses a date with an explicit time zone and optional UTC offset attached (e.g."2021-11-07T00:45[America/Los_Angeles]"
or"2021-11-07T00:45-07:00[America/Los_Angeles]"
). This format preserves the maximum amount of information. If the exact local time and time zone that a user selected is important, use this format. Storing the time zone and offset that was selected rather than converting to UTC ensures that the local time is correct regardless of daylight saving rule changes (e.g. if a locale abolishes DST). Examples where this applies include calendar events, reminders, and other times that occur in a particular location.parseAbsolute
– This function parses an absolute date and time that occurs at the same instant at all locations on Earth. It can be represented in UTC (e.g."2021-11-07T07:45:00Z"
), or stored with a particular offset (e.g."2021-11-07T07:45:00-07:00"
). A time zone identifier, e.g.America/Los_Angeles
, must be passed, and the result will be converted into that time zone. Absolute times are the best way to represent events that occurred in the past, or future events where an exact time is needed, regardless of time zone.parseAbsoluteToLocal
– This function parses an absolute date and time into the current user's local time zone. It is a shortcut forparseAbsolute
, and accepts the same formats.
import {parseZonedDateTime} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseZonedDateTime('2022-11-07T00:45[America/Los_Angeles]'),
end: parseZonedDateTime('2022-11-08T11:15[America/Los_Angeles]')
}} />
import {parseZonedDateTime} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseZonedDateTime(
'2022-11-07T00:45[America/Los_Angeles]'
),
end: parseZonedDateTime(
'2022-11-08T11:15[America/Los_Angeles]'
)
}}
/>
import {parseZonedDateTime} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start:
parseZonedDateTime(
'2022-11-07T00:45[America/Los_Angeles]'
),
end:
parseZonedDateTime(
'2022-11-08T11:15[America/Los_Angeles]'
)
}}
/>
DateRangePicker
displays times in the time zone included in the ZonedDateTime
object. The above example is always displayed in Pacific Standard Time because the America/Los_Angeles
time zone identifier is provided. @internationalized/date includes functions for converting dates between time zones, or parsing a date directly into a specific time zone or the user's local time zone, as shown below.
import {parseAbsoluteToLocal} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseAbsoluteToLocal('2021-11-07T07:45:00Z'),
end: parseAbsoluteToLocal('2021-11-08T14:25:00Z')
}}
/>
import {parseAbsoluteToLocal} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseAbsoluteToLocal('2021-11-07T07:45:00Z'),
end: parseAbsoluteToLocal('2021-11-08T14:25:00Z')
}}
/>
import {parseAbsoluteToLocal} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
defaultValue={{
start:
parseAbsoluteToLocal(
'2021-11-07T07:45:00Z'
),
end:
parseAbsoluteToLocal(
'2021-11-08T14:25:00Z'
)
}}
/>
Granularity#
The granularity
prop allows you to control the smallest unit that is displayed by DateRangePicker
. By default, CalendarDate
values are displayed with "day"
granularity (year, month, and day), and CalendarDateTime
and ZonedDateTime
values are displayed with "minute"
granularity. More granular time values can be displayed by setting the granularity
prop to "second"
.
In addition, when a value with a time is provided but you wish to only display the date, you can set the granularity to "day"
. This has no effect on the actual value (it still has a time component), only on what fields are displayed. In the following example, two DateRangePickers are synchronized with the same value, but display different granularities.
function Example() {
let [date, setDate] = React.useState({
start: parseAbsoluteToLocal('2021-04-07T18:45:22Z'),
end: parseAbsoluteToLocal('2021-04-08T20:00:00Z')
});
return (
<>
<MyDateRangePicker
label="Date and time range"
granularity="second" value={date}
onChange={setDate} />
<MyDateRangePicker
label="Date range"
granularity="day" value={date}
onChange={setDate} />
</>
);
}
function Example() {
let [date, setDate] = React.useState({
start: parseAbsoluteToLocal('2021-04-07T18:45:22Z'),
end: parseAbsoluteToLocal('2021-04-08T20:00:00Z')
});
return (
<>
<MyDateRangePicker
label="Date and time range"
granularity="second" value={date}
onChange={setDate} />
<MyDateRangePicker
label="Date range"
granularity="day" value={date}
onChange={setDate} />
</>
);
}
function Example() {
let [date, setDate] =
React.useState({
start:
parseAbsoluteToLocal(
'2021-04-07T18:45:22Z'
),
end:
parseAbsoluteToLocal(
'2021-04-08T20:00:00Z'
)
});
return (
<>
<MyDateRangePicker
label="Date and time range"
granularity="second" value={date}
onChange={setDate}
/>
<MyDateRangePicker
label="Date range"
granularity="day" value={date}
onChange={setDate}
/>
</>
);
}
If no value
or defaultValue
prop is passed, then the granularity
prop also affects which type of value is emitted from the onChange
event. Note that by default, time values will not have a time zone because none was supplied. You can override this by setting the placeholderValue
prop explicitly. Values emitted from onChange
will use the time zone of the placeholder value.
import {now} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
granularity="second" />
<MyDateRangePicker
label="Date range"
placeholderValue={now('America/New_York')}
granularity="second" />
import {now} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
granularity="second" />
<MyDateRangePicker
label="Date range"
placeholderValue={now('America/New_York')}
granularity="second" />
import {now} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
granularity="second"
/>
<MyDateRangePicker
label="Date range"
placeholderValue={now(
'America/New_York'
)}
granularity="second"
/>
International calendars#
DateRangePicker
supports selecting dates in many calendar systems used around the world, including Gregorian, Hebrew, Indian, Islamic, Buddhist, and more. Dates are automatically displayed in the appropriate calendar system for the user's locale. The calendar system can be overridden using the Unicode calendar locale extension, passed to the I18nProvider component.
Selected dates passed to onChange
always use the same calendar system as the value
or defaultValue
prop. If no value
or defaultValue
is provided, then dates passed to onChange
are always in the Gregorian calendar since this is the most commonly used. This means that even though the user selects dates in their local calendar system, applications are able to deal with dates from all users consistently.
The below example displays a DateRangePicker
in the Hindi language, using the Indian calendar. Dates emitted from onChange
are in the Gregorian calendar.
import type {DateRange} from 'react-aria-components';
import {I18nProvider} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState<DateRange | null>(null);
return (
<I18nProvider locale="hi-IN-u-ca-indian"> <MyDateRangePicker label="Date range" value={range} onChange={setRange} />
<p>Start date: {range?.start.toString()}</p>
<p>End date: {range?.end.toString()}</p>
</I18nProvider>
);
}
import type {DateRange} from 'react-aria-components';
import {I18nProvider} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState<DateRange | null>(
null
);
return (
<I18nProvider locale="hi-IN-u-ca-indian"> <MyDateRangePicker
label="Date range"
value={range}
onChange={setRange}
/>
<p>Start date: {range?.start.toString()}</p>
<p>End date: {range?.end.toString()}</p>
</I18nProvider>
);
}
import type {DateRange} from 'react-aria-components';
import {I18nProvider} from '@react-aria/i18n';
function Example() {
let [range, setRange] =
React.useState<
DateRange | null
>(null);
return (
<I18nProvider locale="hi-IN-u-ca-indian"> <MyDateRangePicker
label="Date range"
value={range}
onChange={setRange}
/>
<p>
Start date:{' '}
{range?.start
.toString()}
</p>
<p>
End date:{' '}
{range?.end
.toString()}
</p>
</I18nProvider>
);
}
HTML forms#
DateRangePicker supports the startName
and endName
props for integration with HTML forms. The values will be submitted to the server as ISO 8601 formatted strings according to the granularity of the value. For example, if the date range picker allows selecting only dates then strings such as "2023-02-03"
will be submitted, and if it allows selecting times then strings such as "2023-02-03T08:45:00"
will be submitted. See the Value section above for more details about the supported value types.
<MyDateRangePicker
label="Trip dates"
startName="startDate"
endName="endDate"
/>
<MyDateRangePicker
label="Trip dates"
startName="startDate"
endName="endDate"
/>
<MyDateRangePicker
label="Trip dates"
startName="startDate"
endName="endDate"
/>
Events#
DateRangePicker
accepts an onChange
prop which is triggered whenever the start or end date is edited by the user. The example below uses onChange
to update a separate element with a formatted version of the date range in the user's locale and local time zone. This is done by converting the dates to native JavaScript Date
objects to pass to the formatter.
import {getLocalTimeZone} from '@internationalized/date';
import {useDateFormatter} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState({
start: parseDate('2020-07-03'),
end: parseDate('2020-07-10')
});
let formatter = useDateFormatter({ dateStyle: 'long' });
return (
<>
<MyDateRangePicker label="Date range" value={range} onChange={setRange} />
<p>
Selected date: {range
? formatter.formatRange(
range.start.toDate(getLocalTimeZone()),
range.end.toDate(getLocalTimeZone())
)
: '--'}
</p>
</>
);
}
import {getLocalTimeZone} from '@internationalized/date';
import {useDateFormatter} from '@react-aria/i18n';
function Example() {
let [range, setRange] = React.useState({
start: parseDate('2020-07-03'),
end: parseDate('2020-07-10')
});
let formatter = useDateFormatter({ dateStyle: 'long' });
return (
<>
<MyDateRangePicker
label="Date range"
value={range}
onChange={setRange}
/>
<p>
Selected date: {range
? formatter.formatRange(
range.start.toDate(getLocalTimeZone()),
range.end.toDate(getLocalTimeZone())
)
: '--'}
</p>
</>
);
}
import {getLocalTimeZone} from '@internationalized/date';
import {useDateFormatter} from '@react-aria/i18n';
function Example() {
let [range, setRange] =
React.useState({
start: parseDate(
'2020-07-03'
),
end: parseDate(
'2020-07-10'
)
});
let formatter =
useDateFormatter({
dateStyle: 'long'
});
return (
<>
<MyDateRangePicker
label="Date range"
value={range}
onChange={setRange}
/>
<p>
Selected date:
{' '}
{range
? formatter
.formatRange(
range.start
.toDate(
getLocalTimeZone()
),
range.end
.toDate(
getLocalTimeZone()
)
)
: '--'}
</p>
</>
);
}
Validation#
Minimum and maximum values#
The minValue
and maxValue
props can also be used to perform builtin validation. This prevents the user from selecting dates outside the valid range in the calendar, and marks the date fields as invalid using ARIA. DateRangePicker
also validates that the end date is after the start date. You should implement a visual indication that the date range picker is invalid as well.
This example only accepts dates after today.
import {today} from '@internationalized/date';
<MyDateRangePicker
label="Trip dates"
minValue={today(getLocalTimeZone())} defaultValue={{
start: parseDate('2022-02-03'),
end: parseDate('2022-05-03')
}} />
import {today} from '@internationalized/date';
<MyDateRangePicker
label="Trip dates"
minValue={today(getLocalTimeZone())} defaultValue={{
start: parseDate('2022-02-03'),
end: parseDate('2022-05-03')
}} />
import {today} from '@internationalized/date';
<MyDateRangePicker
label="Trip dates"
minValue={today(
getLocalTimeZone()
)} defaultValue={{
start: parseDate(
'2022-02-03'
),
end: parseDate(
'2022-05-03'
)
}}
/>
Unavailable dates#
DateRangePicker
supports marking certain dates as unavailable. These dates remain focusable with the keyboard in the calendar so that navigation is consistent, but cannot be selected by the user. The isDateUnavailable
prop accepts a callback that is called to evaluate whether each visible date is unavailable.
Note that by default, users may not select non-contiguous ranges, i.e. ranges that contain unavailable dates within them. Once a start date is selected in the calendar, enabled dates will be restricted to subsequent dates until an unavailable date is hit. While this is handled automatically in the calendar, additional validation logic must be provided to ensure an invalid state is displayed in the date field. This can be achieved using the isInvalid
prop. See below for an example of how to allow non-contiguous ranges.
This example includes multiple unavailable date ranges, e.g. dates when a rental house is not available. The minValue
prop is also used to prevent selecting dates before today. The isInvalid
prop is used to mark selected date ranges with unavailable dates in the middle as invalid.
import type {DateRange} from 'react-aria-components';
import {today} from '@internationalized/date';
function Example() {
let now = today(getLocalTimeZone());
let disabledRanges = [
[now, now.add({ days: 5 })],
[now.add({ days: 14 }), now.add({ days: 16 })],
[now.add({ days: 23 }), now.add({ days: 24 })]
];
let isDateUnavailable = (date: DateValue) =>
disabledRanges.some((interval) =>
date.compare(interval[0]) >= 0 && date.compare(interval[1]) <= 0
);
let [value, setValue] = React.useState<DateRange | null>(null);
let isInvalid = disabledRanges.some((interval) =>
value && value.end.compare(interval[0]) >= 0 &&
value.start.compare(interval[1]) <= 0
);
return (
<MyDateRangePicker
label="Trip dates"
minValue={today(getLocalTimeZone())}
isDateUnavailable={isDateUnavailable} value={value}
onChange={setValue}
isInvalid={isInvalid}
/>
);
}
import type {DateRange} from 'react-aria-components';
import {today} from '@internationalized/date';
function Example() {
let now = today(getLocalTimeZone());
let disabledRanges = [
[now, now.add({ days: 5 })],
[now.add({ days: 14 }), now.add({ days: 16 })],
[now.add({ days: 23 }), now.add({ days: 24 })]
];
let isDateUnavailable = (date: DateValue) =>
disabledRanges.some((interval) =>
date.compare(interval[0]) >= 0 &&
date.compare(interval[1]) <= 0
);
let [value, setValue] = React.useState<DateRange | null>(
null
);
let isInvalid = disabledRanges.some((interval) =>
value && value.end.compare(interval[0]) >= 0 &&
value.start.compare(interval[1]) <= 0
);
return (
<MyDateRangePicker
label="Trip dates"
minValue={today(getLocalTimeZone())}
isDateUnavailable={isDateUnavailable} value={value}
onChange={setValue}
isInvalid={isInvalid}
/>
);
}
import type {DateRange} from 'react-aria-components';
import {today} from '@internationalized/date';
function Example() {
let now = today(
getLocalTimeZone()
);
let disabledRanges = [
[
now,
now.add({
days: 5
})
],
[
now.add({
days: 14
}),
now.add({
days: 16
})
],
[
now.add({
days: 23
}),
now.add({
days: 24
})
]
];
let isDateUnavailable =
(date: DateValue) =>
disabledRanges
.some((
interval
) =>
date.compare(
interval[0]
) >= 0 &&
date.compare(
interval[1]
) <= 0
);
let [value, setValue] =
React.useState<
DateRange | null
>(null);
let isInvalid =
disabledRanges.some(
(interval) =>
value &&
value.end
.compare(
interval[0]
) >= 0 &&
value.start
.compare(
interval[1]
) <= 0
);
return (
<MyDateRangePicker
label="Trip dates"
minValue={today(
getLocalTimeZone()
)}
isDateUnavailable={isDateUnavailable} value={value}
onChange={setValue}
isInvalid={isInvalid}
/>
);
}
Non-contiguous ranges#
The allowsNonContiguousRanges
prop enables a range to be selected even if there are unavailable dates in the middle. The value emitted in the onChange
event will still be a single range with a start
and end
property, but unavailable dates will not be displayed as selected. It is up to applications to split the full selected range into multiple as needed for business logic.
This example prevents selecting weekends, but allows selecting ranges that span multiple weeks.
import {isWeekend} from '@internationalized/date';
import {useLocale} from '@react-aria/i18n';
function Example() {
let {locale} = useLocale();
return (
<MyDateRangePicker
label="Time off request"
isDateUnavailable={date => isWeekend(date, locale)}
allowsNonContiguousRanges /> );
}
import {isWeekend} from '@internationalized/date';
import {useLocale} from '@react-aria/i18n';
function Example() {
let {locale} = useLocale();
return (
<MyDateRangePicker
label="Time off request"
isDateUnavailable={date => isWeekend(date, locale)}
allowsNonContiguousRanges /> );
}
import {isWeekend} from '@internationalized/date';
import {useLocale} from '@react-aria/i18n';
function Example() {
let { locale } =
useLocale();
return (
<MyDateRangePicker
label="Time off request"
isDateUnavailable={(date) =>
isWeekend(
date,
locale
)}
allowsNonContiguousRanges
/> );
}
Help text#
The description
slot can be used to associate additional help text with a date range picker. Additionally, the errorMessage
slot can be used to help the user fix a validation error. It should be combined with the isInvalid
prop to semantically mark the date range picker as invalid for assistive technologies.
This example validates that the selected date range is a maximum of 1 week in duration.
import {today} from '@internationalized/date';
function Example() {
let [range, setRange] = React.useState({
start: today(getLocalTimeZone()),
end: today(getLocalTimeZone()).add({ weeks: 1, days: 3 })
});
let isInvalid = range?.end.compare(range.start) > 7;
return (
<MyDateRangePicker
label="Trip dates"
value={range}
onChange={setRange}
isInvalid={isInvalid}
description={isInvalid ? undefined : 'Select your vacation dates'}
errorMessage={isInvalid ? 'Maximum stay duration is 1 week' : undefined} />
);
}
import {today} from '@internationalized/date';
function Example() {
let [range, setRange] = React.useState({
start: today(getLocalTimeZone()),
end: today(getLocalTimeZone()).add({
weeks: 1,
days: 3
})
});
let isInvalid = range?.end.compare(range.start) > 7;
return (
<MyDateRangePicker
label="Trip dates"
value={range}
onChange={setRange}
isInvalid={isInvalid}
description={isInvalid
? undefined
: 'Select your vacation dates'}
errorMessage={isInvalid
? 'Maximum stay duration is 1 week'
: undefined} />
);
}
import {today} from '@internationalized/date';
function Example() {
let [range, setRange] =
React.useState({
start: today(
getLocalTimeZone()
),
end: today(
getLocalTimeZone()
).add({
weeks: 1,
days: 3
})
});
let isInvalid =
range?.end.compare(
range.start
) > 7;
return (
<MyDateRangePicker
label="Trip dates"
value={range}
onChange={setRange}
isInvalid={isInvalid}
description={isInvalid
? undefined
: 'Select your vacation dates'}
errorMessage={isInvalid
? 'Maximum stay duration is 1 week'
: undefined} />
);
}
Format options#
Placeholder value#
When no value is set, a placeholder is shown. The format of the placeholder is influenced by the granularity
and placeholderValue
props. placeholderValue
also controls the default values of each segment when the user first interacts with them, e.g. using the up and down arrow keys, as well as the default month shown in the calendar popover. By default, the placeholderValue
is the current date at midnight, but you can set it to a more appropriate value if needed.
import {CalendarDate} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
placeholderValue={new CalendarDate(1980, 1, 1)}
/>
import {CalendarDate} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
placeholderValue={new CalendarDate(1980, 1, 1)}
/>
import {CalendarDate} from '@internationalized/date';
<MyDateRangePicker
label="Date range"
placeholderValue={new CalendarDate(
1980,
1,
1
)}
/>
Hide time zone#
When ZonedDateTime
objects are provided as the value of to DateRangePicker
, the time zone abbreviation is displayed by default. However, if this is displayed elsewhere or implicit based on the usecase, it can be hidden using the hideTimeZone
option.
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseZonedDateTime('2022-11-07T10:45[America/Los_Angeles]'),
end: parseZonedDateTime('2022-11-08T19:45[America/Los_Angeles]')
}}
hideTimeZone />
<MyDateRangePicker
label="Date range"
defaultValue={{
start: parseZonedDateTime(
'2022-11-07T10:45[America/Los_Angeles]'
),
end: parseZonedDateTime(
'2022-11-08T19:45[America/Los_Angeles]'
)
}}
hideTimeZone
/>
<MyDateRangePicker
label="Date range"
defaultValue={{
start:
parseZonedDateTime(
'2022-11-07T10:45[America/Los_Angeles]'
),
end:
parseZonedDateTime(
'2022-11-08T19:45[America/Los_Angeles]'
)
}}
hideTimeZone
/>
Hour cycle#
By default, DateRangePicker
displays times in either 12 or 24 hour hour format depending on the user's locale. However, this can be overridden using the hourCycle
prop if needed for a specific usecase. This example forces the DateRangePicker
to use 24-hour time, regardless of the locale.
<MyDateRangePicker
label="Date range"
granularity="minute"
hourCycle={24} />
<MyDateRangePicker
label="Date range"
granularity="minute"
hourCycle={24} />
<MyDateRangePicker
label="Date range"
granularity="minute"
hourCycle={24} />
Props#
DateRangePicker#
Name | Type | Default | Description |
startName | string | — | The name of the start date input element, used when submitting an HTML form. See MDN. |
endName | string | — | The name of the end date input element, used when submitting an HTML form. See MDN. |
pageBehavior | PageBehavior | visible | Controls the behavior of paging. Pagination either works by advancing the visible page by visibleDuration (default) or one unit of visibleDuration. |
minValue | DateValue | — | The minimum allowed date that a user may select. |
maxValue | DateValue | — | The maximum allowed date that a user may select. |
isDateUnavailable | (
(date: DateValue
)) => boolean | — | Callback that is called for each date of the calendar. If it returns true, then the date is unavailable. |
placeholderValue | DateValue | — | A placeholder date that influences the format of the placeholder shown when no value is selected. Defaults to today's date at midnight. |
hourCycle | 12 | 24 | — | Whether to display the time in 12 or 24 hour format. By default, this is determined by the user's locale. |
granularity | Granularity | — | Determines the smallest unit that is displayed in the date picker. By default, this is "day" for dates, and "minute" for times. |
hideTimeZone | boolean | false | Whether to hide the time zone abbreviation. |
shouldForceLeadingZeros | boolean | — | Whether to always show leading zeros in the month, day, and hour fields. By default, this is determined by the user's locale. |
isDisabled | boolean | — | Whether the input is disabled. |
isReadOnly | boolean | — | Whether the input can be selected but not changed by the user. |
isRequired | boolean | — | Whether user input is required on the input before form submission. |
isInvalid | boolean | — | Whether the input value is invalid. |
autoFocus | boolean | — | Whether the element should receive focus on render. |
isOpen | boolean | — | Whether the overlay is open by default (controlled). |
defaultOpen | boolean | — | Whether the overlay is open by default (uncontrolled). |
allowsNonContiguousRanges | boolean | — | When combined with |
value | RangeValue<DateValue> | null | — | The current value (controlled). |
defaultValue | RangeValue<DateValue> | null | — | The default value (uncontrolled). |
children | ReactNode | (
(values: DateRangePickerRenderProps
)) => ReactNode | — | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: DateRangePickerRenderProps
)) => string | — | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: DateRangePickerRenderProps
)) => CSSProperties | — | The inline style for the element. A function may be provided to compute the style based on component state. |
Events
Name | Type | Description |
onFocus | (
(e: FocusEvent<Target>
)) => void | Handler that is called when the element receives focus. |
onBlur | (
(e: FocusEvent<Target>
)) => void | Handler that is called when the element loses focus. |
onFocusChange | (
(isFocused: boolean
)) => void | Handler that is called when the element's focus status changes. |
onKeyDown | (
(e: KeyboardEvent
)) => void | Handler that is called when a key is pressed. |
onKeyUp | (
(e: KeyboardEvent
)) => void | Handler that is called when a key is released. |
onOpenChange | (
(isOpen: boolean
)) => void | Handler that is called when the overlay's open state changes. |
onChange | (
(value: RangeValue<MappedDateValue<DateValue>>
)) => void | Handler that is called when the value changes. |
Layout
Name | Type | Description |
slot | string | null | A slot name for the component. Slots allow the component to receive props from a parent component.
An explicit |
Accessibility
Name | Type | Description |
id | string | The element's unique identifier. See MDN. |
aria-label | string | Defines a string value that labels the current element. |
aria-labelledby | string | Identifies the element (or elements) that labels the current element. |
aria-describedby | string | Identifies the element (or elements) that describes the object. |
aria-details | string | Identifies the element (or elements) that provide a detailed, extended description for the object. |
Label#
A <Label>
accepts all HTML attributes.
Group#
A <Group>
accepts all HTML attributes.
DateInput#
The <DateInput>
component renders a group of date segments. It accepts a function as its children
, which is called to render a <DateSegment>
for each segment. The slot="start"
and slot="end"
props distinguish the two instances within a DateRangePicker
.
Show props
Name | Type | Description |
children | (
(segment: DateSegment
)) => ReactElement | |
className | string | (
(values: DateInputRenderProps
)) => string | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: DateInputRenderProps
)) => CSSProperties | The inline style for the element. A function may be provided to compute the style based on component state. |
DateSegment#
The <DateSegment>
component renders an individual segment.
Show props
Name | Type | Description |
segment | DateSegment | |
children | ReactNode | (
(values: DateSegmentRenderProps
)) => ReactNode | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: DateSegmentRenderProps
)) => string | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: DateSegmentRenderProps
)) => CSSProperties | The inline style for the element. A function may be provided to compute the style based on component state. |
Button#
A <Button>
accepts its contents as children
. Other props such as onPress
and isDisabled
will be set by the DateRangePicker
or RangeCalendar
.
Show props
Name | Type | Default | Description |
form | string | — | The element to associate the button with. The value of this attribute must be the id of a in the same document. |
formAction | string | — | The URL that processes the information submitted by the button. Overrides the action attribute of the button's form owner. |
formEncType | string | — | Indicates how to encode the form data that is submitted. |
formMethod | string | — | Indicates the HTTP method used to submit the form. |
formNoValidate | boolean | — | Indicates that the form is not to be validated when it is submitted. |
formTarget | string | — | Overrides the target attribute of the button's form owner. |
name | string | — | Submitted as a pair with the button's value as part of the form data. |
value | string | — | The value associated with the button's name when it's submitted with the form data. |
isDisabled | boolean | — | Whether the button is disabled. |
autoFocus | boolean | — | Whether the element should receive focus on render. |
type | 'button'
| 'submit'
| 'reset' | 'button' | The behavior of the button when used in an HTML form. |
children | ReactNode | (
(values: ButtonRenderProps
)) => ReactNode | — | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: ButtonRenderProps
)) => string | — | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: ButtonRenderProps
)) => CSSProperties | — | The inline style for the element. A function may be provided to compute the style based on component state. |
Events
Name | Type | Description |
onPress | (
(e: PressEvent
)) => void | Handler that is called when the press is released over the target. |
onPressStart | (
(e: PressEvent
)) => void | Handler that is called when a press interaction starts. |
onPressEnd | (
(e: PressEvent
)) => void | Handler that is called when a press interaction ends, either over the target or when the pointer leaves the target. |
onPressChange | (
(isPressed: boolean
)) => void | Handler that is called when the press state changes. |
onPressUp | (
(e: PressEvent
)) => void | Handler that is called when a press is released over the target, regardless of whether it started on the target or not. |
onFocus | (
(e: FocusEvent<Target>
)) => void | Handler that is called when the element receives focus. |
onBlur | (
(e: FocusEvent<Target>
)) => void | Handler that is called when the element loses focus. |
onFocusChange | (
(isFocused: boolean
)) => void | Handler that is called when the element's focus status changes. |
onKeyDown | (
(e: KeyboardEvent
)) => void | Handler that is called when a key is pressed. |
onKeyUp | (
(e: KeyboardEvent
)) => void | Handler that is called when a key is released. |
Layout
Name | Type | Description |
slot | string | null | A slot name for the component. Slots allow the component to receive props from a parent component.
An explicit |
Accessibility
Name | Type | Description |
id | string | The element's unique identifier. See MDN. |
excludeFromTabOrder | boolean | Whether to exclude the element from the sequential tab order. If true, the element will not be focusable via the keyboard by tabbing. This should be avoided except in rare scenarios where an alternative means of accessing the element or its functionality via the keyboard is available. |
aria-expanded | boolean
| 'true'
| 'false' | Indicates whether the element, or another grouping element it controls, is currently expanded or collapsed. |
aria-haspopup | boolean
| 'menu'
| 'listbox'
| 'tree'
| 'grid'
| 'dialog'
| 'true'
| 'false' | Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an element. |
aria-controls | string | Identifies the element (or elements) whose contents or presence are controlled by the current element. |
aria-pressed | boolean
| 'true'
| 'false'
| 'mixed' | Indicates the current "pressed" state of toggle buttons. |
aria-label | string | Defines a string value that labels the current element. |
aria-labelledby | string | Identifies the element (or elements) that labels the current element. |
aria-describedby | string | Identifies the element (or elements) that describes the object. |
aria-details | string | Identifies the element (or elements) that provide a detailed, extended description for the object. |
Popover#
A <Popover>
is an overlay to hold the <Calendar>
, positioned relative to the <Group>
. By default, it has a placement
of bottom start
within a <DateRangePicker>
, but this and other positioning properties may be customized.
Show props
Name | Type | Default | Description |
triggerRef | RefObject<Element> | — | The ref for the element which the popover positions itself with respect to. When used within a trigger component such as DialogTrigger, MenuTrigger, Select, etc., this is set automatically. It is only required when used standalone. |
placement | Placement | 'bottom' | The placement of the element with respect to its anchor element. |
containerPadding | number | 12 | The placement padding that should be applied between the element and its surrounding container. |
offset | number | 0 | The additional offset applied along the main axis between the element and its anchor element. |
crossOffset | number | 0 | The additional offset applied along the cross axis between the element and its anchor element. |
shouldFlip | boolean | true | Whether the element should flip its orientation (e.g. top to bottom or left to right) when there is insufficient room for it to render completely. |
isNonModal | boolean | — | Whether the popover is non-modal, i.e. elements outside the popover may be interacted with by assistive technologies. Most popovers should not use this option as it may negatively impact the screen reader experience. Only use with components such as combobox, which are designed to handle this situation carefully. |
isKeyboardDismissDisabled | boolean | false | Whether pressing the escape key to close the popover should be disabled. Most popovers should not use this option. When set to true, an alternative way to close the popover with a keyboard must be provided. |
arrowSize | number | 0 | Cross size of the overlay arrow in pixels. |
boundaryElement | Element | document.body | Element that that serves as the positioning boundary. |
scrollRef | RefObject<Element> | overlayRef | A ref for the scrollable region within the overlay. |
shouldUpdatePosition | boolean | true | Whether the overlay should update its position automatically. |
arrowBoundaryOffset | number | 0 | The minimum distance the arrow's edge should be from the edge of the overlay element. |
isOpen | boolean | — | Whether the overlay is open by default (controlled). |
defaultOpen | boolean | — | Whether the overlay is open by default (uncontrolled). |
children | ReactNode | (
(values: PopoverRenderProps
)) => ReactNode | — | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: PopoverRenderProps
)) => string | — | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: PopoverRenderProps
)) => CSSProperties | — | The inline style for the element. A function may be provided to compute the style based on component state. |
Events
Name | Type | Description |
onOpenChange | (
(isOpen: boolean
)) => void | Handler that is called when the overlay's open state changes. |
Layout
Name | Type | Description |
slot | string | null | A slot name for the component. Slots allow the component to receive props from a parent component.
An explicit |
Sizing
Name | Type | Description |
maxHeight | number | The maxHeight specified for the overlay element. By default, it will take all space up to the current viewport height. |
Dialog#
A <Dialog>
is placed within a <Popover>
to hold the <Calendar>
for a DateRangePicker.
Show props
Name | Type | Description |
children | ReactNode | (
(opts: DialogRenderProps
)) => ReactNode | Children of the dialog. A function may be provided to access a function to close the dialog. |
className | string | The CSS className for the element. |
style | CSSProperties | The inline style for the element. |
Layout
Name | Type | Description |
slot | string | null | A slot name for the component. Slots allow the component to receive props from a parent component.
An explicit |
Accessibility
Name | Type | Default | Description |
role | 'dialog' | 'alertdialog' | 'dialog' | The accessibility role for the dialog. |
id | string | — | The element's unique identifier. See MDN. |
aria-label | string | — | Defines a string value that labels the current element. |
aria-labelledby | string | — | Identifies the element (or elements) that labels the current element. |
aria-describedby | string | — | Identifies the element (or elements) that describes the object. |
aria-details | string | — | Identifies the element (or elements) that provide a detailed, extended description for the object. |
RangeCalendar#
A <RangeCalendar>
accepts one or more month grids as chilren, along with previous and next buttons to navigate forward and backward.
Show props
Name | Type | Default | Description |
visibleDuration | DateDuration | {months: 1} | The amount of days that will be displayed at once. This affects how pagination works. |
minValue | DateValue | — | The minimum allowed date that a user may select. |
maxValue | DateValue | — | The maximum allowed date that a user may select. |
isDateUnavailable | (
(date: DateValue
)) => boolean | — | Callback that is called for each date of the calendar. If it returns true, then the date is unavailable. |
isDisabled | boolean | false | Whether the calendar is disabled. |
isReadOnly | boolean | false | Whether the calendar value is immutable. |
autoFocus | boolean | false | Whether to automatically focus the calendar when it mounts. |
focusedValue | DateValue | — | Controls the currently focused date within the calendar. |
defaultFocusedValue | DateValue | — | The date that is focused when the calendar first mounts (uncountrolled). |
isInvalid | boolean | — | Whether the current selection is invalid according to application logic. |
pageBehavior | PageBehavior | visible | Controls the behavior of paging. Pagination either works by advancing the visible page by visibleDuration (default) or one unit of visibleDuration. |
value | DateValue | null | — | The current value (controlled). |
defaultValue | DateValue | null | — | The default value (uncontrolled). |
children | ReactNode | (
(values: CalendarRenderProps
)) => ReactNode | — | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: CalendarRenderProps
)) => string | — | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: CalendarRenderProps
)) => CSSProperties | — | The inline style for the element. A function may be provided to compute the style based on component state. |
Events
Name | Type | Description |
onFocusChange | (
(date: CalendarDate
)) => void | Handler that is called when the focused date changes. |
onChange | (
(value: MappedDateValue<DateValue>
)) => void | Handler that is called when the value changes. |
CalendarGrid#
A <CalendarGrid>
renders an individual month within a <RangeCalendar>
. It accepts a function as its children
, which is called to render a <CalendarCell>
for each date. This renders a default <CalendarGridHeader>
, which displays the weekday names in the column headers. This can be customized by providing a <CalendarGridHeader>
and <CalendarGridBody>
as children instead of a function.
Show props
Name | Type | Default | Description |
children | ReactElement
| ReactElement[]
| (
(date: CalendarDate
)) => ReactElement | — | Either a function to render calendar cells for each date in the month,
or children containing a |
offset | DateDuration | — | An offset from the beginning of the visible date range that this CalendarGrid should display. Useful when displaying more than one month at a time. |
weekdayStyle | 'narrow'
| 'short'
| 'long' | "narrow" | The style of weekday names to display in the calendar grid header, e.g. single letter, abbreviation, or full day name. |
className | string | — | The CSS className for the element. |
style | CSSProperties | — | The inline style for the element. |
CalendarGridHeader#
A <CalendarGridHeader>
renders the header within a <CalendarGrid>
, displaying a list of weekday names. It accepts a function as its children
, which is called with a day name abbreviation to render a <CalendarHeaderCell>
for each column header.
Show props
Name | Type | Description |
children | (
(day: string
)) => ReactElement | A function to render a <CalendarHeaderCell> for a weekday name. |
className | string | The CSS className for the element. |
style | CSSProperties | The inline style for the element. |
CalendarHeaderCell#
A <CalendarHeaderCell>
renders a column header within a <CalendarGridHeader>
. It typically displays a weekday name.
Show props
Name | Type | Description |
children | ReactNode | The children of the component. |
className | string | The CSS className for the element. |
style | CSSProperties | The inline style for the element. |
CalendarGridBody#
A <CalendarGridBody>
renders the body within a <CalendarGrid>
. It accepts a function as its children
, which is called to render a <CalendarCell>
for each date.
Show props
Name | Type | Description |
children | (
(date: CalendarDate
)) => ReactElement | A function to render a <CalendarCell> for a given date. |
className | string | The CSS className for the element. |
style | CSSProperties | The inline style for the element. |
CalendarCell#
A <CalendarCell>
renders an individual date within a <CalendarGrid>
.
Show props
Name | Type | Description |
date | CalendarDate | The date to render in the cell. |
children | ReactNode | (
(values: CalendarCellRenderProps
)) => ReactNode | The children of the component. A function may be provided to alter the children based on component state. |
className | string | (
(values: CalendarCellRenderProps
)) => string | The CSS className for the element. A function may be provided to compute the class based on component state. |
style | CSSProperties | (
(values: CalendarCellRenderProps
)) => CSSProperties | The inline style for the element. A function may be provided to compute the style based on component state. |
Styling#
React Aria components can be styled in many ways, including using CSS classes, inline styles, utility classes (e.g. Tailwind), CSS-in-JS (e.g. Styled Components), etc. By default, all components include a builtin className
attribute which can be targeted using CSS selectors. These follow the react-aria-ComponentName
naming convention.
.react-aria-DateRangePicker {
/* ... */
}
.react-aria-DateRangePicker {
/* ... */
}
.react-aria-DateRangePicker {
/* ... */
}
A custom className
can also be specified on any component. This overrides the default className
provided by React Aria with your own.
<DateInput className="my-date-input">
{/* ... */}
</DateInput>
<DateInput className="my-date-input">
{/* ... */}
</DateInput>
<DateInput className="my-date-input">
{/* ... */}
</DateInput>
In addition, some components support multiple UI states (e.g. focused, placeholder, readonly, etc.). React Aria components expose states using data attributes, which you can target in CSS selectors. For example:
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[data-readonly] {
/* ... */
}
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[data-readonly] {
/* ... */
}
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[data-readonly] {
/* ... */
}
The className
and style
props also accept functions which receive states for styling. This lets you dynamically determine the classes or styles to apply, which is useful when using utility CSS libraries like Tailwind.
<DateSegment
className={({ isPlaceholder }) =>
isPlaceholder ? 'bg-gray-300' : 'bg-gray-600'}
/>
<DateSegment
className={({ isPlaceholder }) =>
isPlaceholder ? 'bg-gray-300' : 'bg-gray-600'}
/>
<DateSegment
className={(
{ isPlaceholder }
) =>
isPlaceholder
? 'bg-gray-300'
: 'bg-gray-600'}
/>
Render props may also be used as children to alter what elements are rendered based on the current state. For example, you could render the placeholder as a separate element to always reserve space for it.
<DateSegment>
{({ text, placeholder, isPlaceholder }) => (
<>
<span style={{ visibility: isPlaceholder ? 'visible' : 'hidden' }}>
{placeholder}
</span>
{isPlaceholder ? '' : text}
</>
)}
</DateSegment>
<DateSegment>
{({ text, placeholder, isPlaceholder }) => (
<>
<span
style={{
visibility: isPlaceholder ? 'visible' : 'hidden'
}}
>
{placeholder}
</span>
{isPlaceholder ? '' : text}
</>
)}
</DateSegment>
<DateSegment>
{(
{
text,
placeholder,
isPlaceholder
}
) => (
<>
<span
style={{
visibility:
isPlaceholder
? 'visible'
: 'hidden'
}}
>
{placeholder}
</span>
{isPlaceholder
? ''
: text}
</>
)}
</DateSegment>
The states, selectors, and render props for each component used in a DateRangePicker
are documented below.
DateRangePicker#
A DateRangePicker
can be targeted with the .react-aria-DateRangePicker
CSS selector, or by overriding with a custom className
. It supports the following states and render props:
Name | CSS Selector | Description |
state | — | State of the date range picker. |
isFocusWithin | [data-focus-within] | Whether an element within the date picker is focused, either via a mouse or keyboard. |
isFocusVisible | [data-focus-visible] | Whether an element within the date picker is keyboard focused. |
isDisabled | [data-disabled] | Whether the date picker is disabled. |
isInvalid | [data-disabled] | Whether the date picker is invalid. |
isOpen | [data-open] | Whether the date picker's popover is currently open. |
Label#
A Label
can be targeted with the .react-aria-Label
CSS selector, or by overriding with a custom className
.
Group#
A Group
can be targeted with the .react-aria-Group
selector, or by overriding with a custom className
. It supports the following states:
Name | CSS Selector | Description |
isHovered | [data-hovered] | Whether the group is currently hovered with a mouse. |
isFocusWithin | [data-focus-within] | Whether an element within the group is focused, either via a mouse or keyboard. |
isFocusVisible | [data-focus-visible] | Whether an element within the group is keyboard focused. |
isDisabled | [data-disabled] | Whether the group is disabled. |
isInvalid | [data-invalid] | Whether the group is invalid. |
DateInput#
A DateInput
can be targeted with the .react-aria-DateInput
CSS selector, or by overriding with a custom className
. It supports the following states:
Name | CSS Selector | Description |
isHovered | [data-hovered] | Whether the date input is currently hovered with a mouse. |
isFocusWithin | [data-focus-within] | Whether an element within the date input is focused, either via a mouse or keyboard. |
isFocusVisible | [data-focus-visible] | Whether an element within the date input is keyboard focused. |
isDisabled | [data-disabled] | Whether the date input is disabled. |
DateSegment#
A DateSegment
can be targeted with the .react-aria-DateSegment
CSS selector, or by overriding with a custom className
. It supports the following states and render props:
Name | CSS Selector | Description |
isHovered | [data-hovered] | Whether the segment is currently hovered with a mouse. |
isFocused | [data-focused] | Whether the segment is focused, either via a mouse or keyboard. |
isFocusVisible | [data-focus-visible] | Whether the segment is keyboard focused. |
isPlaceholder | [data-placeholder] | Whether the value is a placeholder. |
isReadOnly | [data-readonly] | Whether the segment is read only. |
isInvalid | [data-invalid] | Whether the date field is in an invalid state. |
type | [data-type="..."] | The type of segment. Values include literal , year , month , day , etc. |
text | — | The formatted text for the segment. |
placeholder | — | A placeholder string for the segment. |
Button#
A Button can be targeted with the .react-aria-Button
CSS selector, or by overriding with a custom className
. The next and previous buttons within a range calendar can be targeted specifically with the [slot=previous]
and [slot=next]
selectors. Buttons support the following states:
Name | CSS Selector | Description |
isHovered | [data-hovered] | Whether the button is currently hovered with a mouse. |
isPressed | [data-pressed] | Whether the button is currently in a pressed state. |
isFocused | [data-focused] | Whether the button is focused, either via a mouse or keyboard. |
isFocusVisible | [data-focus-visible] | Whether the button is keyboard focused. |
isDisabled | [data-disabled] | Whether the button is disabled. |
Popover#
The Popover component can be targeted with the .react-aria-Popover
CSS selector, or by overriding with a custom className
. Note that it renders in a React Portal, so it will not appear as a descendant of the DateRangePicker in the DOM. It supports the following states and render props:
Name | CSS Selector | Description |
placement | [data-placement="left | right | top | bottom"] | The placement of the popover relative to the trigger. |
isEntering | [data-entering] | Whether the popover is currently entering. Use this to apply animations. |
isExiting | [data-exiting] | Whether the popover is currently exiting. Use this to apply animations. |
Dialog#
A Dialog can be targeted with the .react-aria-Dialog
CSS selector, or by overriding with a custom className
.
RangeCalendar#
A RangeCalendar can be targeted with the .react-aria-RangeCalendar
CSS selector, or by overriding with a custom className
.
CalendarGrid#
A CalendarGrid
can be targeted with the .react-aria-CalendarGrid
CSS selector, or by overriding with a custom className
. When a function is provided as children, a default <CalendarGridHeader>
and <CalendarGridBody>
are rendered. If you need to customize the styling of the header cells, you can render them yourself. See the RangeCalendar docs for an example.
CalendarGridHeader#
A CalendarGridHeader
can be targeted with the .react-aria-CalendarGridHeader
CSS selector, or by overriding with a custom className
.
CalendarHeaderCell#
A CalendarHeaderCell
can be targeted with the .react-aria-CalendarHeaderCell
CSS selector, or by overriding with a custom className
.
CalendarGridBody#
A CalendarGridBody
can be targeted with the .react-aria-CalendarGridBody
CSS selector, or by overriding with a custom className
.
CalendarCell#
A CalendarCell
can be targeted with the .react-aria-CalendarCell
CSS selector, or by overriding with a custom className
. It supports the following states:
Name | CSS Selector | Description |
date | — | The date that the cell represents. |
formattedDate | — | The day number formatted according to the current locale. |
isHovered | [data-hovered] | Whether the cell is currently hovered with a mouse. |
isPressed | [data-pressed] | Whether the cell is currently being pressed. |
isSelected | [data-selected] | Whether the cell is selected. |
isSelectionStart | [data-selection-start] | Whether the cell is the first date in a range selection. |
isSelectionEnd | [data-selection-end] | Whether the cell is the last date in a range selection. |
isFocused | [data-focused] | Whether the cell is focused. |
isFocusVisible | [data-focus-visible] | Whether the cell is keyboard focused. |
isDisabled | [data-disabled] | Whether the cell is disabled, according to the calendar's |
isOutsideVisibleRange | [data-outside-visible-range] | Whether the cell is outside the visible range of the calendar. For example, dates before the first day of a month in the same week. |
isOutsideMonth | [data-outside-month] | Whether the cell is outside the current month. |
isUnavailable | [data-unavailable] | Whether the cell is unavailable, according to the calendar's Note that because they are focusable, unavailable dates must meet a 4.5:1 color contrast ratio, as defined by WCAG. |
isInvalid | [data-invalid] | Whether the cell is part of an invalid selection. |
Text#
The help text elements within a DateRangePicker
can be targeted with the [slot=description]
and [slot=errorMessage]
CSS selectors, or by adding a custom className
.
Advanced customization#
Composition#
If you need to customize one of the components within a DateRangePicker
, such as Label
or DateSegment
, in many cases you can create a wrapper component. This lets you customize the props passed to the component.
function MyDateSegment(props) {
return <MyDateSegment {...props} className="my-date-segment" />
}
function MyDateSegment(props) {
return (
<MyDateSegment {...props} className="my-date-segment" />
);
}
function MyDateSegment(
props
) {
return (
<MyDateSegment
{...props}
className="my-date-segment"
/>
);
}
Contexts#
All React Aria Components export a corresponding context that can be used to send props to them from a parent element. This enables you to build your own compositional APIs similar to those found in React Aria Components itself. You can send any prop or ref via context that you could pass to the corresponding component. The local props and ref on the component are merged with the ones passed via context, with the local props taking precedence (following the rules documented in mergeProps).
Component | Context | Props | Ref |
DateRangePicker | DateRangePickerContext | DateRangePickerProps | HTMLDivElement |
This example shows a FieldGroup
component that renders a group of date pickers with a title and optional error message. It uses the useId hook to generate a unique id for the error message. All of the child DateRangePickers are marked invalid and associated with the error message via the aria-describedby
attribute passed to the DateRangePickerContext
provider.
import {DateRangePickerContext} from 'react-aria-components';
import {useId} from 'react-aria';
interface FieldGroupProps {
title?: string;
children?: React.ReactNode;
errorMessage?: string;
}
function FieldGroup({ title, children, errorMessage }: FieldGroupProps) {
let errorId = useId();
return (
<fieldset>
<legend>{title}</legend>
<DateRangePickerContext.Provider
value={{
isInvalid: !!errorMessage,
'aria-describedby': errorMessage ? errorId : undefined
}}
> {children}
</DateRangePickerContext.Provider>
{errorMessage && (
<small id={errorId} className="invalid">{errorMessage}</small>
)}
</fieldset>
);
}
<FieldGroup
title="Dates"
errorMessage="Ticket sale and event dates cannot overlap."
>
<MyDateRangePicker
label="Ticket sale dates"
defaultValue={{
start: parseDate('2023-07-12'),
end: parseDate('2023-08-04')
}}
/>
<MyDateRangePicker
label="Event dates"
defaultValue={{
start: parseDate('2023-08-01'),
end: parseDate('2023-08-10')
}}
/>
</FieldGroup>
import {DateRangePickerContext} from 'react-aria-components';
import {useId} from 'react-aria';
interface FieldGroupProps {
title?: string;
children?: React.ReactNode;
errorMessage?: string;
}
function FieldGroup(
{ title, children, errorMessage }: FieldGroupProps
) {
let errorId = useId();
return (
<fieldset>
<legend>{title}</legend>
<DateRangePickerContext.Provider
value={{
isInvalid: !!errorMessage,
'aria-describedby': errorMessage
? errorId
: undefined
}}
> {children}
</DateRangePickerContext.Provider>
{errorMessage && (
<small id={errorId} className="invalid">
{errorMessage}
</small>
)}
</fieldset>
);
}
<FieldGroup
title="Dates"
errorMessage="Ticket sale and event dates cannot overlap."
>
<MyDateRangePicker
label="Ticket sale dates"
defaultValue={{
start: parseDate('2023-07-12'),
end: parseDate('2023-08-04')
}}
/>
<MyDateRangePicker
label="Event dates"
defaultValue={{
start: parseDate('2023-08-01'),
end: parseDate('2023-08-10')
}}
/>
</FieldGroup>
import {DateRangePickerContext} from 'react-aria-components';
import {useId} from 'react-aria';
interface FieldGroupProps {
title?: string;
children?:
React.ReactNode;
errorMessage?: string;
}
function FieldGroup(
{
title,
children,
errorMessage
}: FieldGroupProps
) {
let errorId = useId();
return (
<fieldset>
<legend>
{title}
</legend>
<DateRangePickerContext.Provider
value={{
isInvalid:
!!errorMessage,
'aria-describedby':
errorMessage
? errorId
: undefined
}}
> {children}
</DateRangePickerContext.Provider>
{errorMessage && (
<small
id={errorId}
className="invalid"
>
{errorMessage}
</small>
)}
</fieldset>
);
}
<FieldGroup
title="Dates"
errorMessage="Ticket sale and event dates cannot overlap."
>
<MyDateRangePicker
label="Ticket sale dates"
defaultValue={{
start: parseDate(
'2023-07-12'
),
end: parseDate(
'2023-08-04'
)
}}
/>
<MyDateRangePicker
label="Event dates"
defaultValue={{
start: parseDate(
'2023-08-01'
),
end: parseDate(
'2023-08-10'
)
}}
/>
</FieldGroup>
Show CSS
fieldset {
padding: 1.5em;
width: fit-content;
}
.invalid {
color: var(--spectrum-global-color-red-600);
margin-top: 1em;
display: block;
}
@media (forced-colors: active) {
.invalid {
color: LinkText;
}
}
fieldset {
padding: 1.5em;
width: fit-content;
}
.invalid {
color: var(--spectrum-global-color-red-600);
margin-top: 1em;
display: block;
}
@media (forced-colors: active) {
.invalid {
color: LinkText;
}
}
fieldset {
padding: 1.5em;
width: fit-content;
}
.invalid {
color: var(--spectrum-global-color-red-600);
margin-top: 1em;
display: block;
}
@media (forced-colors: active) {
.invalid {
color: LinkText;
}
}
Custom children#
DateRangePicker passes props to its child components, such as the label and popover, via their associated contexts. These contexts are exported so you can also consume them in your own custom components. This enables you to reuse existing components from your app or component library together with React Aria Components.
Component | Context | Props | Ref |
Label | LabelContext | LabelProps | HTMLLabelElement |
Group | GroupContext | GroupProps | HTMLDivElement |
Button | ButtonContext | ButtonProps | HTMLButtonElement |
Popover | PopoverContext | PopoverProps | HTMLElement |
Dialog | DialogContext | DialogProps | HTMLElement |
RangeCalendar | RangeCalendarContext | RangeCalendarProps | HTMLDivElement |
Text | TextContext | TextProps | HTMLElement |
This example consumes from LabelContext
in an existing styled label component to make it compatible with React Aria Components. The useContextProps
hook merges the local props and ref with the ones provided via context by DateRangePicker.
import type {LabelProps} from 'react-aria-components';
import {LabelContext, useContextProps} from 'react-aria-components';
const MyCustomLabel = React.forwardRef(
(props: LabelProps, ref: React.ForwardedRef<HTMLLabelElement>) => {
// Merge the local props and ref with the ones provided via context.
[props, ref] = useContextProps(props, ref, LabelContext);
// ... your existing Label component
return <label {...props} ref={ref} />;
}
);
import type {LabelProps} from 'react-aria-components';
import {
LabelContext,
useContextProps
} from 'react-aria-components';
const MyCustomLabel = React.forwardRef(
(
props: LabelProps,
ref: React.ForwardedRef<HTMLLabelElement>
) => {
// Merge the local props and ref with the ones provided via context.
[props, ref] = useContextProps(
props,
ref,
LabelContext
);
// ... your existing Label component
return <label {...props} ref={ref} />;
}
);
import type {LabelProps} from 'react-aria-components';
import {
LabelContext,
useContextProps
} from 'react-aria-components';
const MyCustomLabel =
React.forwardRef(
(
props: LabelProps,
ref:
React.ForwardedRef<
HTMLLabelElement
>
) => {
// Merge the local props and ref with the ones provided via context.
[props, ref] =
useContextProps(
props,
ref,
LabelContext
);
// ... your existing Label component
return (
<label
{...props}
ref={ref}
/>
);
}
);
Now you can use MyCustomLabel
within a DateRangePicker
, in place of the builtin React Aria Components Label
.
<DateRangePicker>
<MyCustomLabel>Name</MyCustomLabel> {/* ... */}
</DateRangePicker>
<DateRangePicker>
<MyCustomLabel>Name</MyCustomLabel> {/* ... */}
</DateRangePicker>
<DateRangePicker>
<MyCustomLabel>
Name
</MyCustomLabel> {/* ... */}
</DateRangePicker>
State#
DateRangePicker provides a DateRangePickerState
object to its children via DateRangePickerStateContext
. This can be used to access and manipulate the date range picker's state.
This example shows a DateRangePickerClearButton
component that can be placed within a DateRangePicker
to allow the user to clear the selected value.
import {DateRangePickerStateContext} from 'react-aria-components';
function DateRangePickerClearButton() {
let state = React.useContext(DateRangePickerStateContext)!; return (
<Button
// Don't inherit default Button behavior from DateRangePicker.
slot={null}
className="clear-button"
aria-label="Clear"
onPress={() => state.setValue(null)}
>
✕
</Button>
);
}
<DateRangePicker
defaultValue={{
start: parseDate('2023-07-12'),
end: parseDate('2023-08-04')
}}
>
<Label>Trip dates</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<DateRangePickerClearButton /> <Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {DateRangePickerStateContext} from 'react-aria-components';
function DateRangePickerClearButton() {
let state = React.useContext(
DateRangePickerStateContext
)!; return (
<Button
// Don't inherit default Button behavior from DateRangePicker.
slot={null}
className="clear-button"
aria-label="Clear"
onPress={() => state.setValue(null)}
>
✕
</Button>
);
}
<DateRangePicker
defaultValue={{
start: parseDate('2023-07-12'),
end: parseDate('2023-08-04')
}}
>
<Label>Trip dates</Label>
<Group>
<DateInput slot="start">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<span aria-hidden="true">–</span>
<DateInput slot="end">
{(segment) => <DateSegment segment={segment} />}
</DateInput>
<DateRangePickerClearButton /> <Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">◀</Button>
<Heading />
<Button slot="next">▶</Button>
</header>
<CalendarGrid>
{(date) => <CalendarCell date={date} />}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
import {DateRangePickerStateContext} from 'react-aria-components';
function DateRangePickerClearButton() {
let state = React
.useContext(
DateRangePickerStateContext
)!; return (
<Button
// Don't inherit default Button behavior from DateRangePicker.
slot={null}
className="clear-button"
aria-label="Clear"
onPress={() =>
state.setValue(
null
)}
>
✕
</Button>
);
}
<DateRangePicker
defaultValue={{
start: parseDate(
'2023-07-12'
),
end: parseDate(
'2023-08-04'
)
}}
>
<Label>
Trip dates
</Label>
<Group>
<DateInput slot="start">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<span aria-hidden="true">
–
</span>
<DateInput slot="end">
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
<DateRangePickerClearButton /> <Button>▼</Button>
</Group>
<Popover>
<Dialog>
<RangeCalendar>
<header>
<Button slot="previous">
◀
</Button>
<Heading />
<Button slot="next">
▶
</Button>
</header>
<CalendarGrid>
{(date) => (
<CalendarCell
date={date}
/>
)}
</CalendarGrid>
</RangeCalendar>
</Dialog>
</Popover>
</DateRangePicker>
Show CSS
.clear-button {
width: 1.143rem;
height: 1.143rem;
border-radius: 1.143rem;
font-size: 0.857rem;
line-height: 0.857rem;
vertical-align: middle;
text-align: center;
background: gray;
color: white;
border: none;
padding: 0;
outline: none;
&[data-pressed] {
background: dimgray;
}
&[data-focus-visible] {
outline: 2px solid slateblue;
outline-offset: 2px;
}
+ .react-aria-Button {
margin-left: 4px;
}
}
.clear-button {
width: 1.143rem;
height: 1.143rem;
border-radius: 1.143rem;
font-size: 0.857rem;
line-height: 0.857rem;
vertical-align: middle;
text-align: center;
background: gray;
color: white;
border: none;
padding: 0;
outline: none;
&[data-pressed] {
background: dimgray;
}
&[data-focus-visible] {
outline: 2px solid slateblue;
outline-offset: 2px;
}
+ .react-aria-Button {
margin-left: 4px;
}
}
.clear-button {
width: 1.143rem;
height: 1.143rem;
border-radius: 1.143rem;
font-size: 0.857rem;
line-height: 0.857rem;
vertical-align: middle;
text-align: center;
background: gray;
color: white;
border: none;
padding: 0;
outline: none;
&[data-pressed] {
background: dimgray;
}
&[data-focus-visible] {
outline: 2px solid slateblue;
outline-offset: 2px;
}
+ .react-aria-Button {
margin-left: 4px;
}
}
Hooks#
If you need to customize things even further, such as accessing internal state, intercepting events, or customizing the DOM structure, you can drop down to the lower level Hook-based API. See useDateRangePicker for more details.