import type { ControlSize } from "@charcuterie/tokens";
import type { ReactNode } from "react";
import type { SlotProps } from "../slotProps.ts";
import type { TimecodeRange } from "./timecode.ts";
export type TimecodeInputProps = SlotProps & {
    className?: string;
    /**
     * How long the media is. It is the default `maxValueMs`, so a
     * consumer that knows the file's length gets the clamp without
     * stating a bound twice.
     */
    durationMs?: number;
    isDisabled?: boolean;
    /**
     * Section mode — a start and an end. A **mode, not a sibling
     * component**, following `DatePicker`'s `isRange` and `Combobox`'s
     * `isMultiple`.
     */
    isRange?: boolean;
    /**
     * Required. In section mode it names **both** inputs, as
     * "<label> start" and "<label> end", so the two stay separately
     * addressable by a screen reader and by an agent.
     */
    label: string;
    /** The end of the allowed window. Defaults to `durationMs`. */
    maxValueMs?: number;
    /** The start of the allowed window. Defaults to `0`. */
    minValueMs?: number;
    /**
     * Milliseconds in single mode, a `{ end, start }` of them in
     * section mode, and `null` when both ends are cleared.
     */
    onChange?: (value: null | number | TimecodeRange) => void;
    placeholder?: string;
    size?: ControlSize;
    /** How far ArrowUp and ArrowDown move. Shift multiplies it by ten. */
    stepMs?: number;
    /** **Initial** only, like every other value prop in this library. */
    valueMs?: number | TimecodeRange;
};
/**
 * A timecode field: a text input a person can actually type a media
 * position into, with an `isRange` mode for a section of a file.
 *
 * ### Why this is a text field and not `<input type="time">`
 *
 * Two reasons and neither is taste.
 *
 * A `time` input's smallest step is a **second** unless `step` is
 * fractional, its value is a wall-clock `HH:MM` string capped at 24
 * hours, and it has no way to express "1.5 hours into a file" as a
 * duration rather than as half past one. A clip boundary in a video
 * editor is milliseconds; the platform control cannot carry them.
 *
 * And it is painted by the operating system, from
 * `::-webkit-datetime-edit-*` pseudo-elements no token reaches
 * inside — the same mechanism that
 * [deprecated the native `Select`](../../../../docs/decisions/2026-08-20-native-select-is-deprecated-and-the-platform-hatch-is-closed.md)
 * and that kept `Slider` off
 * [`<input type="range">`](../../../../docs/decisions/2026-08-22-the-slider-is-a-div-with-role-slider-not-an-input-range.md).
 * A `<input type="text">` this component owns every pixel of is the
 * settled answer to that shape of question.
 *
 * ### Typing is the whole interface, so nothing guesses in silence
 *
 * `90`, `1:30`, `1:02:03` and `1:02:03.500` all resolve, and the
 * resolution is echoed underneath the field, in a live region, before
 * anything commits. Commit is Enter or blur; a keystroke never
 * commits, a refused value leaves the text exactly as typed, and
 * Escape puts back the last committed value. `timecode.ts` is the
 * grammar and the reasoning.
 *
 * ### Both ends of a section are independently optional
 *
 * `{ end, start }` has four real states, not three plus an error: no
 * window, from here to the end of the media, from the beginning up to
 * here, and the window between two points. So there is no
 * `isEndOpen` prop — `null` says it — and clearing one end never
 * touches the other.
 *
 * An **inverted** section swaps, because throwing the pair away would
 * discard the boundary just typed. A **zero-length** section is
 * refused by name: it plays nothing, so swapping would hide a typo
 * behind a window that silently does not exist.
 *
 * ### The Narrow View stacks the two fields
 *
 * Below `--cq-sm` a section is two fields one above the other, under
 * the captions "Start" and "End"; above it, the row with `to`
 * between them. It is a **container** query, so a 390px modal on a
 * 2560px monitor gets the stacked form that a window breakpoint
 * would have denied it. The captions are `aria-hidden`, so the
 * accessible name of each control is the same in both layouts.
 *
 * ### Milliseconds are optional to read as well as to type
 *
 * The grammar has always accepted `1:01:00`. The field now writes it
 * back as `01:01:00` rather than as `01:01:00.000`, through
 * `formatTimecode`'s `millisecondDigits: "auto"`, because a fraction
 * nobody typed is not information. `1:01:00.5` still commits as
 * `01:01:00.500`.
 */
export declare const TimecodeInput: ({ className, durationMs, isDisabled, isRange, label, maxValueMs, minValueMs, onChange, placeholder, size, stepMs, valueMs, ...receivedSlotProps }: TimecodeInputProps) => ReactNode;
//# sourceMappingURL=TimecodeInput.d.ts.map