TimeField
A time field allows users to enter and edit time values using a keyboard. Each part of a time value is displayed in an individually editable segment.
install | yarn add react-aria-components |
---|---|
version | 3.17.0 |
usage | import {TimeField} from 'react-aria-components' |
Example#
import {TimeField, Label, DateInput, DateSegment} from 'react-aria-components';
<TimeField>
<Label>Event time</Label>
<DateInput>
{segment => <DateSegment segment={segment} />}
</DateInput>
</TimeField>
import {
DateInput,
DateSegment,
Label,
TimeField
} from 'react-aria-components';
<TimeField>
<Label>Event time</Label>
<DateInput>
{(segment) => <DateSegment segment={segment} />}
</DateInput>
</TimeField>
import {
DateInput,
DateSegment,
Label,
TimeField
} from 'react-aria-components';
<TimeField>
<Label>
Event time
</Label>
<DateInput>
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
</TimeField>
Show CSS
.react-aria-DateInput {
display: flex;
padding: 4px;
border: 1px solid var(--spectrum-global-color-gray-400);
border-radius: 6px;
background: var(--spectrum-global-color-gray-50);
width: fit-content;
min-width: 150px;
&:focus-within {
border-color: slateblue;
box-shadow: 0 0 0 1px slateblue;
}
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--spectrum-global-color-gray-700);
font-style: italic;
}
&:focus {
color: white;
background: slateblue;
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[aria-invalid] {
color: var(--spectrum-global-color-red-600);
&:focus {
background: var(--spectrum-global-color-static-red-600);
color: white;
}
}
}
.react-aria-TimeField {
& [slot=description] {
font-size: 12px;
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--spectrum-global-color-red-600);
}
}
.react-aria-DateInput {
display: flex;
padding: 4px;
border: 1px solid var(--spectrum-global-color-gray-400);
border-radius: 6px;
background: var(--spectrum-global-color-gray-50);
width: fit-content;
min-width: 150px;
&:focus-within {
border-color: slateblue;
box-shadow: 0 0 0 1px slateblue;
}
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--spectrum-global-color-gray-700);
font-style: italic;
}
&:focus {
color: white;
background: slateblue;
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[aria-invalid] {
color: var(--spectrum-global-color-red-600);
&:focus {
background: var(--spectrum-global-color-static-red-600);
color: white;
}
}
}
.react-aria-TimeField {
& [slot=description] {
font-size: 12px;
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--spectrum-global-color-red-600);
}
}
.react-aria-DateInput {
display: flex;
padding: 4px;
border: 1px solid var(--spectrum-global-color-gray-400);
border-radius: 6px;
background: var(--spectrum-global-color-gray-50);
width: fit-content;
min-width: 150px;
&:focus-within {
border-color: slateblue;
box-shadow: 0 0 0 1px slateblue;
}
}
.react-aria-DateSegment {
padding: 0 2px;
font-variant-numeric: tabular-nums;
text-align: end;
&[data-type=literal] {
padding: 0;
}
&[data-placeholder] {
color: var(--spectrum-global-color-gray-700);
font-style: italic;
}
&:focus {
color: white;
background: slateblue;
outline: none;
border-radius: 4px;
caret-color: transparent;
}
&[aria-invalid] {
color: var(--spectrum-global-color-red-600);
&:focus {
background: var(--spectrum-global-color-static-red-600);
color: white;
}
}
}
.react-aria-TimeField {
& [slot=description] {
font-size: 12px;
}
& [slot=errorMessage] {
font-size: 12px;
color: var(--spectrum-global-color-red-600);
}
}
Features#
A time field can be built using <input type="time">
, but this is very limited in functionality, lacking in internationalization capabilities, inconsistent between browsers, and difficult to style. TimeField
helps achieve accessible and international time fields that can be styled as needed.
- International – Support for locale-specific formatting, number systems, hour cycles, and right-to-left layout.
- Time zone aware – Times can optionally include a time zone. All modifications follow time zone rules such as daylight saving time.
- Accessible – Each time unit is displayed as an individually focusable and editable segment, which allows users an easy way to edit times using the keyboard, in any format and locale.
- Touch friendly – Time segments are editable using an easy to use numeric keypad, 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 TimeField
.
Anatomy#
A time field consists of a label, and a group of segments representing each unit of a time (e.g. hours, minutes, and seconds). Each segment is individually focusable and editable by the user, by typing or using the arrow keys to increment and decrement the value. This approach allows values to be formatted and parsed correctly regardless of the locale or time format, and offers an easy and error-free way to edit times using the keyboard.
TimeField
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.
If the time field 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 DateField, so you can reuse many components between them if you have both.
Concepts#
TimeField
makes use of the following concepts:
Composed components#
A TimeField
uses the following components, which may also be used standalone or reused in other components.
Props#
TimeField#
Name | Type | Default | Description |
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 | 'hour'
| 'minute'
| 'second' | 'minute' | Determines the smallest unit that is displayed in the time picker. |
hideTimeZone | boolean | — | Whether to hide the time zone abbreviation. |
placeholderValue | TimeValue | — | A placeholder time that influences the format of the placeholder shown when no value is selected. Defaults to 12:00 AM or 00:00 depending on the hour cycle. |
minValue | TimeValue | — | The minimum allowed time that a user may select. |
maxValue | TimeValue | — | The maximum allowed time that a user may select. |
isDisabled | boolean | — | Whether the input is disabled. |
isReadOnly | boolean | — | Whether the input can be selected but not changed by the user. |
validationState | ValidationState | — | Whether the input should display its "valid" or "invalid" visual styling. |
isRequired | boolean | — | Whether user input is required on the input before form submission.
Often paired with the |
autoFocus | boolean | — | Whether the element should receive focus on render. |
value | TimeValue | — | The current value (controlled). |
defaultValue | TimeValue | — | The default value (uncontrolled). |
children | ReactNode | (
(values: DateFieldState
)) => ReactNode | — | |
className | string | (
(values: DateFieldState
)) => string | — | |
style | CSSProperties | (
(values: DateFieldState
)) => CSSProperties | — |
Events
Name | Type | Default | Description |
onFocus | (
(e: FocusEvent
)) => void | — | Handler that is called when the element receives focus. |
onBlur | (
(e: FocusEvent
)) => 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. |
onChange | (
(value: MappedTimeValue<TimeValue>
)) => void | — | Handler that is called when the value changes. |
Accessibility
Name | Type | Default | 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.
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.
Show props
Name | Type | Default | Description |
children | (
(segment: DateSegment
)) => ReactElement | — | |
className | string | — | |
style | CSSProperties | — |
Layout
Name | Type | Default | Description |
slot | string | — |
DateSegment#
The <DateSegment>
component renders an individual segment.
Show props
Name | Type | Default | Description |
segment | DateSegment | — | |
children | ReactNode | (
(values: DateSegmentRenderProps
)) => ReactNode | — | |
className | string | (
(values: DateSegmentRenderProps
)) => string | — | |
style | CSSProperties | (
(values: DateSegmentRenderProps
)) => CSSProperties | — |
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-TimeField {
/* ... */
}
.react-aria-TimeField {
/* ... */
}
.react-aria-TimeField {
/* ... */
}
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 DOM attributes, which you can target in CSS selectors. These are ARIA attributes wherever possible, or data attributes when a relevant ARIA attribute does not exist. For example:
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[aria-readonly] {
/* ... */
}
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[aria-readonly] {
/* ... */
}
.react-aria-DateSegment[data-placeholder] {
/* ... */
}
.react-aria-DateSegment[aria-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 TimeField
are documented below.
TimeField#
A TimeField
can be targeted with the .react-aria-TimeField
CSS selector, or by overriding with a custom className
. It provides a DateFieldState
object to its render props, which can be used to customize the className
, style
, or children
.
Label#
A Label
can be targeted with the .react-aria-Label
CSS selector, or by overriding with a custom className
.
DateInput#
A DateInput
can be targeted with the .react-aria-DateInput
CSS selector, or by overriding with a custom className
.
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 |
isPlaceholder | [data-placeholder] | Whether the value is a placeholder. |
isReadOnly | [aria-readonly] | Whether the segment is read only. |
isInvalid | [aria-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. |
value | — | The numeric value for the segment, if applicable. |
minValue | — | The minimum numeric value for the segment, if applicable. |
maxValue | — | The maximum numeric value for the segment, if applicable. |
placeholder | — | A placeholder string for the segment. |
Reusable wrappers#
If you will use a TimeField 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 TimeField
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 {Text} from 'react-aria-components';
function MyTimeField({label, description, errorMessage, ...props}) {
return (
<TimeField {...props}>
<Label>{label}</Label>
<DateInput>
{segment => <DateSegment segment={segment} />}
</DateInput>
{description && <Text slot="description">{description}</Text>}
{errorMessage && <Text slot="errorMessage">{errorMessage}</Text>}
</TimeField>
);
}
<MyTimeField label="Event time" />
import {Text} from 'react-aria-components';
function MyTimeField(
{ label, description, errorMessage, ...props }
) {
return (
<TimeField {...props}>
<Label>{label}</Label>
<DateInput>
{(segment) => <DateSegment segment={segment} />}
</DateInput>
{description && (
<Text slot="description">{description}</Text>
)}
{errorMessage && (
<Text slot="errorMessage">{errorMessage}</Text>
)}
</TimeField>
);
}
<MyTimeField label="Event time" />
import {Text} from 'react-aria-components';
function MyTimeField(
{
label,
description,
errorMessage,
...props
}
) {
return (
<TimeField
{...props}
>
<Label>
{label}
</Label>
<DateInput>
{(segment) => (
<DateSegment
segment={segment}
/>
)}
</DateInput>
{description && (
<Text slot="description">
{description}
</Text>
)}
{errorMessage && (
<Text slot="errorMessage">
{errorMessage}
</Text>
)}
</TimeField>
);
}
<MyTimeField label="Event time" />
Usage#
The following examples show how to use the MyTimeField
component created in the above example.
Value#
A TimeField
displays a placeholder by default. An initial, uncontrolled value can be provided to the TimeField
using the defaultValue
prop. Alternatively, a controlled value can be provided using the value
prop.
Time values are provided using objects in the @internationalized/date package. This library handles correct international date and time manipulation across calendars, time zones, and other localization concerns.
TimeField
only supports selecting times, but values with date components are also accepted. By default, TimeField
will emit Time
objects in the onChange
event, but if a CalendarDateTime
or ZonedDateTime
object is passed as the value
or defaultValue
, values of that type will be emitted, changing only the time and preserving the date components.
import {Time} from '@internationalized/date';
function Example() {
let [value, setValue] = React.useState(new Time(11, 45));
return (
<>
<MyTimeField
label="Time (uncontrolled)"
defaultValue={new Time(11, 45)} />
<MyTimeField
label="Time (controlled)"
value={value}
onChange={setValue} />
</>
);
}
import {Time} from '@internationalized/date';
function Example() {
let [value, setValue] = React.useState(new Time(11, 45));
return (
<>
<MyTimeField
label="Time (uncontrolled)"
defaultValue={new Time(11, 45)} />
<MyTimeField
label="Time (controlled)"
value={value}
onChange={setValue} />
</>
);
}
import {Time} from '@internationalized/date';
function Example() {
let [value, setValue] =
React.useState(
new Time(11, 45)
);
return (
<>
<MyTimeField
label="Time (uncontrolled)"
defaultValue={new Time(
11,
45
)}
/>
<MyTimeField
label="Time (controlled)"
value={value}
onChange={setValue}
/>
</>
);
}
Time
values may also be parsed from strings using the parseTime
function. This accepts ISO 8601 formatted time strings such as "04:45:23.123"
. The toString
method of a Time
object can also be used to convert a time object to a string.
Time zones#
TimeField
is time zone aware when a ZonedDateTime
object is 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';
<MyTimeField
label="Event time"
defaultValue={parseZonedDateTime('2022-11-07T00:45[America/Los_Angeles]')}
/>
import {parseZonedDateTime} from '@internationalized/date';
<MyTimeField
label="Event time"
defaultValue={parseZonedDateTime(
'2022-11-07T00:45[America/Los_Angeles]'
)}
/>
import {parseZonedDateTime} from '@internationalized/date';
<MyTimeField
label="Event time"
defaultValue={parseZonedDateTime(
'2022-11-07T00:45[America/Los_Angeles]'
)}
/>
TimeField
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';
<MyTimeField
label="Event time"
defaultValue={parseAbsoluteToLocal('2021-11-07T07:45:00Z')}
/>
import {parseAbsoluteToLocal} from '@internationalized/date';
<MyTimeField
label="Event time"
defaultValue={parseAbsoluteToLocal(
'2021-11-07T07:45:00Z'
)}
/>
import {parseAbsoluteToLocal} from '@internationalized/date';
<MyTimeField
label="Event time"
defaultValue={parseAbsoluteToLocal(
'2021-11-07T07:45:00Z'
)}
/>
Events#
TimeField
accepts an onChange
prop which is triggered whenever the time is edited by the user. The example below uses onChange
to update a separate element with a formatted version of the date in the user's locale and local time zone. This is done by converting the date to a native JavaScript Date
object to pass to the formatter. TimeField
allows editing the time components while keeping the date fixed.
import {useDateFormatter} from 'react-aria';
import {getLocalTimeZone} from '@internationalized/date';
function Example() {
let [date, setDate] = React.useState(
parseAbsoluteToLocal('2021-04-07T18:45:22Z')
);
let formatter = useDateFormatter({ dateStyle: 'long', timeStyle: 'long' });
return (
<>
<MyTimeField label="Time" value={date} onChange={setDate} />
<p>
Selected date and time:{' '}
{formatter.format(date.toDate(getLocalTimeZone()))}
</p>
</>
);
}
import {useDateFormatter} from 'react-aria';
import {getLocalTimeZone} from '@internationalized/date';
function Example() {
let [date, setDate] = React.useState(
parseAbsoluteToLocal('2021-04-07T18:45:22Z')
);
let formatter = useDateFormatter({
dateStyle: 'long',
timeStyle: 'long'
});
return (
<>
<MyTimeField
label="Time"
value={date}
onChange={setDate}
/>
<p>
Selected date and time:{' '}
{formatter.format(date.toDate(getLocalTimeZone()))}
</p>
</>
);
}
import {useDateFormatter} from 'react-aria';
import {getLocalTimeZone} from '@internationalized/date';
function Example() {
let [date, setDate] =
React.useState(
parseAbsoluteToLocal(
'2021-04-07T18:45:22Z'
)
);
let formatter =
useDateFormatter({
dateStyle: 'long',
timeStyle: 'long'
});
return (
<>
<MyTimeField
label="Time"
value={date}
onChange={setDate}
/>
<p>
Selected date and
time:{' '}
{formatter
.format(
date.toDate(
getLocalTimeZone()
)
)}
</p>
</>
);
}
Granularity#
The granularity
prop allows you to control the smallest unit that is displayed by TimeField
. By default, times are displayed with "minute"
granularity. More granular time values can be displayed by setting the granularity
prop to "second"
.
<MyTimeField
label="Event time"
granularity="second"
defaultValue={parseAbsoluteToLocal('2021-04-07T18:45:22Z')} />
<MyTimeField
label="Event time"
granularity="second"
defaultValue={parseAbsoluteToLocal(
'2021-04-07T18:45:22Z'
)}
/>
<MyTimeField
label="Event time"
granularity="second"
defaultValue={parseAbsoluteToLocal(
'2021-04-07T18:45:22Z'
)}
/>
Minimum and maximum values#
The minValue
and maxValue
props can also be used to perform builtin validation. This marks the time field as invalid using ARIA if the user enters an invalid time. You should implement a visual indication that the time field is invalid as well.
This example only accepts times between 9 AM and 5 PM.
<MyTimeField
label="Meeting time"
minValue={new Time(9)}
maxValue={new Time(17)}
defaultValue={new Time(8)} />
<MyTimeField
label="Meeting time"
minValue={new Time(9)}
maxValue={new Time(17)}
defaultValue={new Time(8)} />
<MyTimeField
label="Meeting time"
minValue={new Time(
9
)}
maxValue={new Time(
17
)}
defaultValue={new Time(
8
)}
/>
Help text#
The description
slot can be used to associate additional help text with a date field. Additionally, the errorMessage
slot can be used to help the user fix a validation error. It should be combined with the validationState
prop to semantically mark the date field as invalid for assistive technologies.
This example validates that the selected time is on a 15 minute increment.
function Example() {
let [time, setTime] = React.useState(new Time(9, 15));
let isInvalid = time.minute % 15;
return (
<MyTimeField
label="Meeting time"
value={time}
onChange={setTime}
validationState={isInvalid ? 'invalid' : 'valid'}
description={isInvalid ? null : 'Select a meeting time'}
errorMessage={isInvalid ? 'Meetings start every 15 minutes.' : null} />
);
}
function Example() {
let [time, setTime] = React.useState(new Time(9, 15));
let isInvalid = time.minute % 15;
return (
<MyTimeField
label="Meeting time"
value={time}
onChange={setTime}
validationState={isInvalid ? 'invalid' : 'valid'}
description={isInvalid
? null
: 'Select a meeting time'}
errorMessage={isInvalid
? 'Meetings start every 15 minutes.'
: null}
/>
);
}
function Example() {
let [time, setTime] =
React.useState(
new Time(9, 15)
);
let isInvalid =
time.minute % 15;
return (
<MyTimeField
label="Meeting time"
value={time}
onChange={setTime}
validationState={isInvalid
? 'invalid'
: 'valid'}
description={isInvalid
? null
: 'Select a meeting time'}
errorMessage={isInvalid
? 'Meetings start every 15 minutes.'
: null}
/>
);
}
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. By default, the placeholderValue
is midnight, but you can set it to a more appropriate value if needed.
<MyTimeField label="Meeting time" placeholderValue={new Time(9)} />
<MyTimeField
label="Meeting time"
placeholderValue={new Time(9)}
/>
<MyTimeField
label="Meeting time"
placeholderValue={new Time(
9
)}
/>
Hide time zone#
When a ZonedDateTime
object is provided as the value to TimeField
, 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.
<MyTimeField
label="Appointment time"
defaultValue={parseZonedDateTime('2022-11-07T10:45[America/Los_Angeles]')}
hideTimeZone />
<MyTimeField
label="Appointment time"
defaultValue={parseZonedDateTime(
'2022-11-07T10:45[America/Los_Angeles]'
)}
hideTimeZone
/>
<MyTimeField
label="Appointment time"
defaultValue={parseZonedDateTime(
'2022-11-07T10:45[America/Los_Angeles]'
)}
hideTimeZone
/>
Hour cycle#
By default, TimeField
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 TimeField
to use 24-hour time, regardless of the locale.
<MyTimeField
label="Appointment time"
hourCycle={24} />
<MyTimeField
label="Appointment time"
hourCycle={24} />
<MyTimeField
label="Appointment time"
hourCycle={24}
/>
Advanced customization#
Composition#
If you need to customize one of the components within a TimeField
, 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"
/>
);
}
Hooks#
If you need to customize things even further, such as accessing internal state or customizing DOM structure, you can drop down to the lower level Hook-based API. See useTimeField for more details.