Skip to main content

DateRangeInput

Overview​

The DateRangeInput component is a form input for a start and end date, picked from one popover calendar or typed into two segmented inputs.

It is built on the same calendar, popover and segmented typing as DateInput, so a stay, a report period or a leave request needs no second input and no hand-rolled check that the end isn't before the start. The calendar picks the start and then the end, previewing the range as you move toward the end, and the range stays ordered whichever way it was entered. min, max and the disabled-date props apply to both ends, a range can't cross a disabled day unless you allow it, and the range submits with a form as two dates.


Import​

import { DateRangeInput } from '@allxsmith/bestax-bulma';

Usage​

Basic DateRangeInput​

Click either input to open the calendar, pick the first day, then the last. Hover a day, or move to it with the arrow keys, to preview the range before you pick it.

function example() {
  return <DateRangeInput label="Stay" placeholder="YYYY-MM-DD" />;
}


Controlled​

The value is a [start, end] pair, and either end can be null. The calendar reports a range once it has both ends. Typing reports each end as it changes, so a range typed halfway arrives as [start, null].

import type { DateRangeValue } from '@allxsmith/bestax-bulma';

function ControlledRange() {
  const [range, setRange] = React.useState<DateRangeValue>([null, null]);
  const [start, end] = range;
  return (
    <Block>
      <DateRangeInput label="Report period" value={range} onChange={setRange} />
      <Paragraph>
        {start ? start.toDateString() : 'No start'} to{' '}
        {end ? end.toDateString() : 'no end'}
      </Paragraph>
      <Button size="small" onClick={() => setRange([null, null])}>
        Clear
      </Button>
    </Block>
  );
}


Inline​

Render the calendar on the page instead of in a popover. There are no inputs, and the form value still submits.

<DateRangeInput label="Stay" inline name="stay" />

On a server-rendered page, an inline calendar marks today once the page hydrates, by the reader's clock rather than the server's. With no value or defaultValue it opens on the month the clock reads, and around the end of a month the server's clock and the reader's can read different months, so give it a date both render the same.


Several Months​

monthsToShow sets months side by side, in the popover and inline, so a range that crosses a month's end shows both its ends. They wrap to a column where the width runs out. The previous button sits on the first month and the next button on the last, and both move every month by monthsToShow. The months start with the range's start as the first, or with an end that has no start as the last. A start typed into the field that isn't on show brings in months with it as the first, so the range runs on from it, and an end brings them in with it as the last. min and max win: the months stay inside them where they leave room for all of them.

<DateRangeInput label="Stay" monthsToShow={2} />

The popover takes the months' width rather than the field's, up to --bulma-picker-popover-months-max-width, the window's width less 2rem, past which they wrap to a column. From a field far from the window's left edge it can reach past the right one: set position="auto", which lines the popover up with the field's right edge when it doesn't fit to the right.


Min and Max​

min and max bound both ends, in the calendar and as you type.

function NextMonth() {
  const today = new Date();
  const inAMonth = new Date();
  inAMonth.setMonth(inAMonth.getMonth() + 1);
  return (
    <DateRangeInput label="Within the next month" min={today} max={inAMonth} />
  );
}


Disabled Dates​

shouldDisableDate and unselectableDates disable days for both ends. By default a range can't include a disabled day either. In the calendar, a pick that can't end the range starts a new one: a day before the start, or one past a disabled day. Typing refuses such an end, and a start typed past the end, or with a disabled day before it, clears the end.

allowDisabledInRange lets a range cross disabled days, for cases such as a stay over a night with no check-ins. Its ends still can't be disabled days.

function Weekdays() {
  const weekend = (d: Date) => d.getDay() === 0 || d.getDay() === 6;
  return (
    <Block>
      <DateRangeInput label="Weekdays only" shouldDisableDate={weekend} />
      <DateRangeInput
        label="Over weekends"
        shouldDisableDate={weekend}
        allowDisabledInRange
      />
    </Block>
  );
}


Typing the Dates​

Each input has the segmented entry DateInput has. With openOnFocus={false} the inputs are for typing, Tab moves from the start input to the end input, and the launcher or Alt+↓ opens the calendar; Alt+↑ closes it. An empty end starts from the start date, so you only type what differs.

<DateRangeInput
  label="Type the dates"
  openOnFocus={false}
  placeholder="YYYY-MM-DD"
/>


Format and Locale​

format, parse and locale work as they do on DateInput, for both inputs, and a LocaleProvider around it sets the locale and first day of the week the same way. The labels keys rangeStart and rangeEnd name the inputs and the range's ends in the calendar, rangePreviewEnd describes the day a pending range would end on, rangeSeparator is the text between the inputs, and chooseDateRange names the launcher.

<DateRangeInput
  label="Séjour"
  locale="fr-FR"
  firstDayOfWeek={1}
  format="DD/MM/YYYY"
  labels={{
    rangeStart: 'Arrivée',
    rangeEnd: 'Départ',
    rangePreviewEnd: 'Choisir comme départ',
    rangeSeparator: 'au',
    chooseDateRange: 'Choisir les dates',
  }}
/>


Mobile Native​

With mobileNative ('auto' by default) a touch device with a small screen gets two native <input type="date">s. The end input's min follows the start, and a change is held to the same rules as typing. Pass true to force them, or false to keep the calendar.

<DateRangeInput label="Stay" mobileNative />


Sizes and Colors​

size and color style the field, and color also fills the range's ends in the calendar and tints the band between them.

<Block>
  <DateRangeInput label="Small" size="small" controlSize="small" />
  <DateRangeInput label="Success" color="success" />
  <DateRangeInput label="Large" size="large" controlSize="large" />
</Block>


Context-Aware Rendering​

Like the other form inputs, DateRangeInput renders its own Field and Control unless it is already inside one.

<Field label="Leave">
  <Control iconLeftName="calendar-alt">
    <DateRangeInput />
  </Control>
</Field>

Inside a Control, DateRangeInput renders no Control of its own, so the props it would hand one, such as isLoading, the icon props, controlSize and controlClassName, do nothing there and warn in development. Set them on that Control instead, as iconLeftName is above. Its default left icon is left out there too, without a warning, since you did not set it. An inline picker renders no Control anywhere, so these props do nothing on it inside a Control or out, and it warns about them too.


Keyboard Navigation​

On the inputs​

Each input takes the keys of DateInput's segmented entry, so Alt+↓ opens the popover and Alt+↑ closes it. Each takes a pasted date the way DateInput does. Moving between the inputs leaves the popover as it is; arriving in the field opens it under openOnFocus, and so does a click on either input.

On the calendar​

Movement is the same as on DateInput's calendar. Picking takes two steps.

KeyAction
Enter / SpaceSet the start, then the end. A day that can't end the range starts a new one
EscapeTake back a start picked in the calendar; with none, close the popover
Alt+↑Close the popover
← / →Move focus by ±1 day, moving the preview with it
↑ / ↓Move focus by ±1 week
PageUp / PageDownMove focus by ±1 month
Shift+PageUp/DownMove focus by ±1 year
Home / EndJump to the start / end of the week

With monthsToShow, the arrow keys cross from one month's grid into the next, and a key that takes focus past the months on show brings that month in: as the first month moving forward, and as the last moving back, as far as min and max leave room. A start picked in the calendar stays while you change month or year, so the end can be in another month. When the range has a start and no end, the calendar opens with that start already picked and the next pick sets the end. That start came from the value rather than from a pick, so Escape closes the popover.


Form Submission​

Give it a name and two hidden inputs submit the range as YYYY-MM-DD, named name[start] and name[end]. They are there in every mode: popover, inline and native, and they submit even while the picker is disabled. Rails, PHP and qs read those names as a nested object, and FormData has them as two entries. startName and endName name either one yourself. The visible inputs carry no name, so the displayed text never submits.

PropDescription
nameNames the hidden inputs name[start] and name[end].
startNameName of the hidden input carrying the start, in place of name[start].
endNameName of the hidden input carrying the end, in place of name[end].
formId of the form the hidden inputs belong to.
requiredMarks both visible inputs required. An inline calendar has no input to mark.
function RangeFormDemo() {
  const [submitted, setSubmitted] = React.useState('');
  return (
    <form
      onSubmit={e => {
        e.preventDefault();
        const data = new FormData(e.currentTarget);
        setSubmitted(JSON.stringify(Array.from(data.entries()), null, 2));
      }}
    >
      <DateRangeInput label="Stay" name="stay" required />
      <Button type="submit" color="primary">
        Submit
      </Button>
      {submitted && <Pre mt="3">{submitted}</Pre>}
    </form>
  );
}


Accessibility​

  • The root is a role="group" named by label through aria-labelledby, since the label names two inputs rather than one. Inside a labeled Field, that Field's label names the group the same way, whether the Field holds DateRangeInput or a DateRangeInputBase you composed in a Control yourself, inline or not. An aria-label or aria-labelledby you give the group wins over either label.
  • Each input is a role="combobox" with aria-haspopup="dialog", aria-expanded and aria-controls, and its own name: "Start date" or "End date", from the labels keys rangeStart and rangeEnd. The separator between them is hidden from assistive technology.
  • aria-invalid and aria-errormessage go on both inputs, marking the range as a whole, while the other attributes you pass go on the group, so a screen reader hears an input is invalid when it takes focus. An inline picker has no input, and they stay on its group.
  • The popover is a role="dialog" named "Choose date range" (labels.chooseDateRange). Opening it puts focus on the calendar's focused day, and closing it returns focus to the input you were last in, or to the start input.
  • With monthsToShow, each month is a grid of its own, named by its month and year, and the calendar keeps one tab stop across them.
  • A day the grid leaves blank, a nearby month's day with nearbyMonthDays off or one whose month is on show beside it, draws nothing. A week left with no day on show keeps its place, so the grid keeps its height and months side by side line up, and is hidden from assistive technology rather than read as an empty row.
  • The day grid is aria-multiselectable, and its days sit in a role="row" per week. Every day of the range is aria-selected, both ends included. While the end is still being picked, only the start is: the preview is not a selection.
  • In forced colors (Windows' contrast themes), the fill and the band that mark the range are replaced, so bestax's styles draw every day of a picked range, both ends included, and the year the header's year list is on, in the system's highlight colors there, or in the system's color for a disabled control when it's disabled. While the end is still being picked, only the start is filled, and the day the range would end on keeps its dashed edge.
  • In forced colors, a disabled day, month or year, a disabled month or arrow button in the header, and a disabled launcher draw in the system's color for a disabled control, at full strength rather than faded.
  • A disabled inline calendar puts aria-disabled="true" on its grid and disables every button in it. A readOnly one puts aria-readonly="true" there instead, keeps its tab stop and keys, and picks nothing.
  • The start and end days are described as "Start date" and "End date", so moving onto either says which it is. While the end is still being picked, the day the range would end on is described as "Choose as end date" (labels.rangePreviewEnd).
  • A polite live region in the calendar states the range in words, such as "Start date: June 10, 2024, End date: June 13, 2024", and announces each pick. The grid points at it too, so moving into the grid reads the current range.
  • Everything else is the calendar DateInput uses: a roving tabindex, weekday column headers named in full (or by your dayNames), aria-disabled on disabled days, aria-current="date" on today, and focus back on the grid as the year list closes.
  • On a right-to-left page the launcher sits at the end of the line and the calendar icon at the start, and the previous-month chevron points right.
  • A panel that would run past the left or right edge of the screen, as on a phone with the field mid-row, keeps its corner and moves sideways just far enough to fit, or, wider than the screen, to the edge its text starts from.
  • The message describes the group through aria-describedby, after any ids you pass there, as the label names it.

  • DateInput - A single date, month or year.
  • DateTimeInput - A date and a time of day.
  • Field - Label, help text and layout for any input.

Additional Resources​


Props​

PropTypeDefaultDescription
labelReact.ReactNode—Field label naming the whole range. Associated through aria-labelledby on the role="group" root, since it names two inputs rather than one; uses your labelProps.id when provided, otherwise a generated one. Each input keeps its own name, "Start date" or "End date" (labels.rangeStart / labels.rangeEnd). Dropped inside an outer Field, whose own label names the group instead through aria-labelledby when that Field generates a target id (not grouped/hasAddons, no explicit labelProps.htmlFor). An aria-label or aria-labelledby you set on the group wins over either label, which still renders but no longer names it. An aria-labelledby key counts even when undefined, since it is spread over the group's own.
labelSize'small' | 'normal' | 'medium' | 'large'—Size for the label.
labelPropsReact.LabelHTMLAttributes<HTMLLabelElement> & { [key: string]: unknown; }—Props for the label element. An htmlFor here is dropped, since the label names the group rather than one input.
horizontalbooleanfalseRender the field with horizontal layout.
iconLeftIconProps | React.ReactNode—Icon props for the left icon. Bulma gives control icons pointer-events: none, so a clickable node here never receives a click. Put a button beside the field in its own addon Control instead.
iconRightIconProps | React.ReactNode—Icon props for the right icon. Bulma gives control icons pointer-events: none, so a clickable node here never receives a click. Put a button beside the field in its own addon Control instead.
iconRightNamestring—Shortcut for the right icon name.
iconLeftSize'small' | 'medium' | 'large'—Shortcut for left icon size.
iconRightSize'small' | 'medium' | 'large'—Shortcut for right icon size.
hasIconsLeftbooleanfalseForce the left icon container.
hasIconsRightbooleanfalseForce the right icon container.
isLoadingbooleanfalseShows a loading spinner on the Control it renders, and hides the launcher (triggerIcon) while it does. Inside your own Control it renders none, so this draws nothing and warns in development; set isLoading on that Control.
triggerIconbooleantrueShow a clickable launcher button on the right that toggles the popover. Hidden by default while a spinner shows at the same right edge: this component's isLoading when it renders its own Control, or the enclosing Control's isLoading inside one.
isExpandedbooleanfalseExpand the control to fill its container.
controlSize'small' | 'medium' | 'large'—Size of the wrapping Control.
messageReact.ReactNode—Help or validation text under the field. It describes the group through aria-describedby, after any ids you pass there.
messageColor'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger'—Color modifier for the help message.
fieldClassNamestring—Additional CSS classes for the Field wrapper.
controlClassNamestring—Additional CSS classes for the Control wrapper.
valueDateRangeValue—Controlled range, start first. Either end may be null, and [null, null] is empty.
defaultValueDateRangeValue—Initial range for uncontrolled usage.
onChange(range: DateRangeValue) => void—Fired when the range changes, with the start first. Typing commits one end at a time, so a range half typed arrives as [start, null]. The calendar commits only a finished range: its first pick marks the start inside the calendar and its second commits both ends in one call. The range stays ordered, so the end is never before the start.
onOpen() => void—Fired when the popover opens.
onClose() => void—Fired when the popover closes.
minDate—Earliest selectable date, for either end. A min before year 1 is raised to 1 January of year 1, where the range starts without one too.
maxDate—Latest selectable date, for either end.
disabledbooleanfalseDisable both inputs and the launcher, or an inline calendar's days and header buttons. The hidden inputs still submit the range, in every mode, where a disabled input submits nothing.
readOnlybooleanfalseMake both inputs read-only and keep the popover closed. An inline calendar still moves through the dates by key and by its header, but a click, Enter or Space picks nothing.
placeholderstring—Placeholder text, shown in both inputs while they are empty.
formatIntl.DateTimeFormatOptions | string'YYYY-MM-DD'Token format string or Intl.DateTimeFormat options, used by both inputs.
parse(s: string) => Date | null—Custom parser (use when format is Intl.DateTimeFormatOptions). Enter and leaving an input call it only if the user changed its text.
localestring—BCP-47 locale tag for day/month names, the digits the calendar numbers its days and years in, and Intl formatting. Unset, it is the locale of a LocaleProvider around the picker, and with neither, Intl uses the runtime's own locale and the calendar numbers its days and years in plain digits. On a server render that locale is the server's, so an inline calendar rendered there names its days in the server's language and the browser's own render names them in the browser's: give it a locale, here or through a LocaleProvider, where the two can differ.
inlinebooleanfalseRender the calendar inline, with no inputs and no popover. The hidden form inputs still carry the range. On a server-rendered page it marks today once the page hydrates, by the browser's clock rather than the server's. With no value or defaultValue it opens on the month the clock reads, and around the end of a month the server's clock and the browser's can read different months, so give it a date both render the same.
mobileNativeboolean | 'auto''auto'Use two native <input type="date">s on coarse-pointer, small-viewport devices ('auto'), always (true) or never (false). The end input's min follows the start, and a change goes through the same rules as typing.
editablebooleantrueAllow segmented keyboard typing in both inputs. false makes the field picker-only.
popoverbooleantrueWhether the calendar popover exists. false makes the field input-only.
openOnFocusbooleantrueOpen the popover when focus arrives in the field. Moving focus between the two inputs, or back from the launcher, leaves it closed, and so does the focus a closing popover hands back. A click on either input opens it. With it off, the launcher or Alt+ArrowDown opens it.
closeOnSelectbooleantrueClose the popover once the range is picked. The first pick, which only marks the start, never closes it.
position'bottom-left' | 'bottom-right' | 'top-left' | 'top-right' | 'auto''bottom-left'Where the popover opens against the field. Left out, it opens below and lines up with the field's start edge, which is its right edge when the picker reads right to left. A corner you pass stays physical, so bottom-left lines up the left edges either way. A panel that would run past the viewport's left or right edge keeps its corner and moves sideways, just far enough to fit or, wider than the viewport, to the edge its text starts from.
appendToBodybooleanfalseRender the popover through a portal, into the portalContainer a ConfigProvider sets, else the overlay it's in that takes its popups, such as a Modal, else document.body.
color'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger'—Bulma color modifier for the field, also carried by the calendar, where it colors the range's ends and the band between them. Forced colors (Windows' contrast themes) replaces both, so there every day of a picked range is drawn in the system's highlight colors instead, whatever the color, which needs bestax's CSS.
size'small' | 'medium' | 'large'—Size variant.
isRoundedbooleanfalseRender the field with rounded corners.
shouldDisableDate(d: Date) => boolean—Predicate to disable specific dates (e.g. weekends). A disabled day can be neither end, typing rejects it, and a range can't include one unless allowDisabledInRange is set.
unselectableDatesDate[]—Convenience array of disabled dates; merged with shouldDisableDate. Matched by calendar day.
allowDisabledInRangebooleanfalseLet a range include days that shouldDisableDate or unselectableDates disable, such as a stay over a night with no check-ins. Its ends still can't be such days. Off, a pick in the calendar past a disabled day starts a new range there, typing refuses an end past one, and a start typed with one before the end clears the end. Finding one walks the days between, so off, a span too long to walk is refused as well.
firstDayOfWeek0 | 1 | 2 | 3 | 4 | 5 | 60Day the week starts on (0 = Sunday). Unset inside a LocaleProvider, it is the first day of the week in the picker's locale, its own locale or else the provider's, such as Monday for "de". Elsewhere, with no locale from either, or with seven dayNames of your own, it is Sunday: set it with dayNames to start the week on another day.
dayNamesstring[]—Override the 7 day-name labels (in calendar order, post-rotation). They are shown exactly as given, from the first column, so they have to start on the day the week does. With them, an unset firstDayOfWeek stays Sunday even inside a LocaleProvider, so names written Sunday first keep matching their columns; to start on the locale's day, set firstDayOfWeek too and list the names from that day. They also name the columns for assistive technology. Without them each column is named by its full weekday in the picker's locale, which a server-rendered calendar adds once the page hydrates.
monthNamesstring[]—Override the 12 month-name labels. With them the day grid's heading reads the name, a space and the year, whatever order the locale writes a month and its year in.
nearbyMonthDaysbooleantrueShow dimmed dates from adjacent months in the grid.
monthsToShownumber1How many months the calendar shows side by side, in the popover and inline, so a range that crosses a month's end shows both its ends. They wrap to a column where the width runs out, one previous and next pair moves them all by this many, and the arrow keys cross from one month into the next. They start with the range's start as the first month, or an end with no start as the last, and a start typed into the field that isn't on show brings in months with it as the first, an end with it as the last. min and max win: the months stay inside them where they leave room for all of them. The popover takes the months' width rather than the field's, up to the window's width less 2rem, so from a field far from the window's left edge it can reach past the right one: set position="auto", which lines the popover up with the field's right edge when it doesn't fit to the right.
iconLeftNamestring'calendar'Decorative left icon glyph for the wrapping Control (shown by default). Set '' to hide.
triggerIconNamestring'chevron-down'Glyph for the right launcher button.
labelsPickerLabels—Optional translatable string overrides. rangeStart and rangeEnd name the two inputs and the range's ends in the calendar, rangePreviewEnd describes the day a pending range would end on, rangeSeparator sits between the inputs, and chooseDateRange names the launcher and the popover.
namestring—Form field name. Two hidden inputs submit the range as YYYY-MM-DD, named name[start] and name[end], in every mode. The visible inputs carry no name.
startNamestring—Name of the hidden input carrying the start, in place of name[start].
endNamestring—Name of the hidden input carrying the end, in place of name[end].
formstring—Form id the hidden inputs belong to.
requiredbooleanfalseMark both visible inputs required, so a form won't submit with either end empty. An inline calendar has no visible input, so it is not checked there.
idReact.HTMLAttributes<HTMLElement>['id']—Id of the start input. The end input takes ${id}-end.
classNamestring—Additional CSS classes for the root, the role="group" that holds the two inputs.
refReact.Ref<HTMLInputElement>—Forwarded to the start <input>.
...All standard <div> attributes and Bulma helper props—Helper props go on the root .daterangeinput <div>, with className and the other attributes, except that the background helpers go on the .input <div> that draws the field around the two <input>s, since Bulma's .input sets its own background. The text helpers go on the root and on both <input>s too, which take no alignment or case from around them. Inline they all go on the root. See Helper Props

CSS & Sass Variables​

DateRangeInput registers these variables on its own .daterangeinput element. Override them there (or via className) — a value set on an ancestor is only inherited, and loses to the component-level declaration. See Theme.

CSS VariableSass VariableDefault
--bulma-calendar-months-gap$calendar-months-gapvar(--bulma-block-spacing)
--bulma-dateinput-min-width ‡$dateinput-min-width16rem
--bulma-dateinput-cell-size ‡$dateinput-cell-size2.25rem
--bulma-dateinput-cell-radius ‡$dateinput-cell-radiusvar(--bulma-radius-small)
--bulma-dateinput-cell-color ‡$dateinput-cell-colorvar(--bulma-text)
--bulma-dateinput-cell-hover-bg ‡$dateinput-cell-hover-bghsla(0, 0%, 50%, 0.13)
--bulma-dateinput-cell-selected-bg ‡$dateinput-cell-selected-bgvar(--bulma-primary)
--bulma-dateinput-cell-selected-color ‡$dateinput-cell-selected-colorvar(--bulma-primary-invert)
--bulma-dateinput-cell-today-color ‡$dateinput-cell-today-colorvar(--bulma-primary-on-scheme)
--bulma-dateinput-focus-ring-color ‡$dateinput-focus-ring-colorvar(--bulma-primary-on-scheme)
--bulma-dateinput-cell-disabled-color ‡$dateinput-cell-disabled-colorvar(--bulma-text-weak)
--bulma-dateinput-cell-other-month-color ‡$dateinput-cell-other-month-colorcolor-mix(in srgb, var(--bulma-text-weak), var(--bulma-text))
--bulma-dateinput-header-padding ‡$dateinput-header-padding0.5rem 0
--bulma-dateinput-day-name-color ‡$dateinput-day-name-colorvar(--bulma-text-weak)
--bulma-dateinput-day-name-size ‡$dateinput-day-name-sizevar(--bulma-size-7)
--bulma-dateinput-nav-button-size ‡$dateinput-nav-button-size1.75rem
--bulma-dateinput-cell-range-bg ‡$dateinput-cell-range-bgcolor-mix(in srgb, var(--bulma-dateinput-cell-selected-bg) 18%, transparent)
--bulma-dateinput-cell-range-preview-bg ‡$dateinput-cell-range-preview-bgcolor-mix(in srgb, var(--bulma-dateinput-cell-selected-bg) 9%, transparent)
--bulma-dateinput-cell-content-color ‡$dateinput-cell-content-colorcolor-mix(in srgb, var(--bulma-text-weak), var(--bulma-text))
--bulma-dateinput-cell-content-size ‡$dateinput-cell-content-sizevar(--bulma-size-7)
--bulma-dateinput-cell-content-loading-opacity ‡$dateinput-cell-content-loading-opacity0.4
--bulma-daterangeinput-gap$daterangeinput-gap0.5em
--bulma-daterangeinput-separator-color$daterangeinput-separator-colorvar(--bulma-text-weak)
--bulma-picker-popover-z-index ‡$picker-popover-z-index30
--bulma-picker-popover-background ‡$picker-popover-backgroundvar(--bulma-scheme-main)
--bulma-picker-popover-radius ‡$picker-popover-radiusvar(--bulma-radius-large)
--bulma-picker-popover-shadow ‡$picker-popover-shadow0 8px 24px hsla(0, 0%, 0%, 0.18)
--bulma-picker-popover-border-color ‡$picker-popover-border-colorvar(--bulma-border)
--bulma-picker-popover-padding ‡$picker-popover-padding0.75rem
--bulma-picker-popover-offset ‡$picker-popover-offset4px
--bulma-picker-popover-animation-duration ‡$picker-popover-animation-duration0.15s
--bulma-picker-popover-months-max-width ‡$picker-popover-months-max-widthcalc(100vw - 2rem)
--bulma-input-h ‡$input-hvar(--bulma-scheme-h)
--bulma-input-s ‡$input-svar(--bulma-scheme-s)
--bulma-input-l ‡$input-lvar(--bulma-scheme-main-l)
--bulma-input-border-style ‡$input-border-stylesolid
--bulma-input-border-width ‡$input-border-widthvar(--bulma-control-border-width)
--bulma-input-border-l ‡$input-border-lvar(--bulma-border-l)
--bulma-input-border-l-delta ‡$input-border-l-delta0%
--bulma-input-border-color ‡$input-border-colorhsl(var(--bulma-input-h), var(--bulma-input-s), calc(var(--bulma-input-border-l) + var(--bulma-input-border-l-delta)))
--bulma-input-hover-border-l-delta ‡$input-hover-border-l-deltavar(--bulma-hover-border-l-delta)
--bulma-input-active-border-l-delta ‡$input-active-border-l-deltavar(--bulma-active-border-l-delta)
--bulma-input-focus-h ‡$input-focus-hvar(--bulma-focus-h)
--bulma-input-focus-s ‡$input-focus-svar(--bulma-focus-s)
--bulma-input-focus-l ‡$input-focus-lvar(--bulma-focus-l)
--bulma-input-focus-shadow-size ‡$input-focus-shadow-sizevar(--bulma-focus-shadow-size)
--bulma-input-focus-shadow-alpha ‡$input-focus-shadow-alphavar(--bulma-focus-shadow-alpha)
--bulma-input-color-l ‡$input-color-lvar(--bulma-text-strong-l)
--bulma-input-background-l ‡$input-background-lvar(--bulma-scheme-main-l)
--bulma-input-background-l-delta ‡$input-background-l-delta0%
--bulma-input-height ‡$input-heightvar(--bulma-control-height)
--bulma-input-shadow ‡$input-shadowinset 0 0.0625em 0.125em hsla(var(--bulma-scheme-h), var(--bulma-scheme-s), var(--bulma-scheme-invert-l), 0.05)
--bulma-input-placeholder-color ‡$input-placeholder-colorhsla(var(--bulma-text-h), var(--bulma-text-s), var(--bulma-text-strong-l), 0.3)
--bulma-input-disabled-color ‡$input-disabled-colorvar(--bulma-text-weak)
--bulma-input-disabled-background-color ‡$input-disabled-background-colorvar(--bulma-background)
--bulma-input-disabled-border-color ‡$input-disabled-border-colorvar(--bulma-background)
--bulma-input-disabled-placeholder-color ‡$input-disabled-placeholder-colorhsla(var(--bulma-text-h), var(--bulma-text-s), var(--bulma-text-weak-l), 0.3)
--bulma-input-arrow ‡$input-arrowvar(--bulma-link)
--bulma-input-icon-color ‡$input-icon-colorvar(--bulma-text-light)
--bulma-input-icon-hover-color ‡$input-icon-hover-colorvar(--bulma-text-weak)
--bulma-input-icon-focus-color ‡$input-icon-focus-colorvar(--bulma-link)
--bulma-input-radius ‡$input-radiusvar(--bulma-radius)

‡ declared on a constituent element: values set via className, the style prop, or an ancestor are only inherited and lose — target the declaring element in your CSS.