Skip to content
MIZU.

RangeSelector

Two bounded handles define an interval without crossing or hiding their values.

View .md

Live — this one is real

Visible window20s — 70s

Usage

tsx
"use client";

import { useState } from "react";
import { RangeSelector } from "mizu-ui";

export function Example() {
  const [value, setValue] = useState<[number, number]>([20, 70]);
  return (
    <RangeSelector
      label="Visible window"
      value={value}
      onValueChange={setValue}
      min={0}
      max={120}
      format={(v) => `${v}s`}
    />
  );
}

It starts with "use client" because it keeps state or passes functions to components, so it pastes into a Next.js page as it is. Other React setups ignore the directive.

Source & setup

Add this component to your project with the shadcn CLI. The command copies its source into your configured UI directory, with base.css, Mizu’s tokens, and the stylesheets that hold its rules. Each rule lives in one stylesheet, so components you add together never repeat CSS. In a project without a components.json, run npx shadcn@latest init 0xuser64bit/mizu/preset first: plain init installs shadcn’s theme into your global CSS. Then load the fonts.

sh
npx shadcn@latest add 0xuser64bit/mizu/range-selector

Every component imports from its own path, its name in kebab case. To paste the example, replace its mizu-ui import with:

tsx
import { RangeSelector } from "@/components/ui/mizu/range-selector";

For npm imports, import mizu-ui/styles.css once. Fonts are optional via mizu-ui/fonts.css. Override --mizu-* tokens or use className for local styling. Uses native React and CSS; install the package peers for root imports. A Client Component: its source starts with “use client”.

Inspect interaction/RangeSelector.tsx

Source is included in the npm package under src/interaction/RangeSelector.tsx.

Open full source ↗

Props

PropTypeDefaultDescription
value / onValueChange[number, number] / function—Controlled start and end.
min / max / stepnumber0 / 100 / 1Full interval and native step.
format(value: number) => string—Visible and announced units.

Accessibility

Two separately labelled native ranges share a fieldset legend. Start is bounded by end, end by start, and each input spans only the stretch of the shared scale it may move along, so both thumbs and the selected window line up. Native keyboard and touch behavior.

Motion

Direct native input.

Works alongside

ComboboxMultiSelectInlineEditReorderList