import type { RefObject } from "react";
/**
 * The track's width, and the font size it is drawn in.
 *
 * ## Measured, because no breakpoint can answer this
 *
 * `Nav` folds its bar on a measured width and
 * `useToolbarOverflow.ts` writes down the general form of the
 * argument: mux-magic collapses at a hardcoded `480px`, plex-channels
 * at `760px`, and neither number has a reason. A timeline has the
 * same problem one level worse, because the question is not "how
 * wide is the box" but **"how wide is one day"** — and that is the
 * width divided by a number that lives in the data. Thirty columns
 * in 900px is a readable month; three hundred and sixty five columns
 * in the same 900px is a grey smear. A media query sees the first
 * number and a container query sees the first number, so neither can
 * decide this.
 *
 * ## Why the font size comes back too
 *
 * The minimum readable column is a multiple of the **type**, not a
 * count of pixels. Every length in this token set moves with the
 * density axis — `--font-size-md` is one thing on a desktop and
 * another on the kiosk — so a column floor pinned at 20px is
 * generous at one density and clips a two-digit date at the next.
 * `Avatar` makes the same argument about a chip that stays 20px
 * while the prose around it scales, and it is the same mistake.
 *
 * ⚠️ **The measured element must not be sized by its own contents.**
 * The timeline reads its own box to decide what to draw in it, so a
 * shrink-wrapping parent makes the answer its own input: fewer
 * columns, narrower box, fewer columns. `LaneTimeline`'s root
 * declares `container-type: inline-size`, which forbids exactly that
 * — the same reason `Main` declares one — so the loop cannot form
 * even when a caller drops the component into a `inline-flex` cell.
 *
 * ## The first paint
 *
 * `useLayoutEffect`, so the measurement lands **before the browser
 * paints** and a timeline that has to fall back to the Narrow View
 * never flashes an unreadable axis first. Same reasoning as
 * `useToolbarOverflow`; the failure it prevents was visible on a
 * kiosk Pi, where a slow first frame is on screen long enough to
 * read.
 *
 * ## ⚠️ `trackRef` goes on a PROBE, never on the real track
 *
 * The one-way trap, and it is not hypothetical — the first draft
 * had it. Attach this to the axis track itself and the Narrow View
 * unmounts the element being measured, so the width never updates
 * again and the timeline can never come back when the window
 * widens. Hiding the track with `display: none` instead is worse: a
 * hidden box measures 0, 0 reads as *unmeasured*, unmeasured shows
 * the axis, the axis hides the fallback, and the component
 * oscillates every frame.
 *
 * So the ref belongs to a zero-height `aria-hidden` cell that sits
 * in the **same grid track** the axis would occupy and is rendered
 * in both layouts. It answers the question actually being asked —
 * *how wide would a day column be if I drew one* — in the layout
 * where no day column exists.
 */
export declare const useTrackMeasurements: () => {
    fontSize: number;
    inlineSize: number;
    isMeasured: boolean;
    trackRef: RefObject<HTMLDivElement | null>;
};
//# sourceMappingURL=useTrackMeasurements.d.ts.map