@nanisoft/prism-ui 0.13.0 → 0.15.0

package/dist/components/ui/text-format-toolbar.d.ts

@@ -0,0 +1,211 @@
+import { type ReactNode } from 'react';
+/**
+ * One command in a text format toolbar: an id, a name, a mark, whether it can run
+ * right now, and what running it does.
+ *
+ * The enabled state is caller data and that is the load-bearing decision. Prism
+ * does not read the selection, cannot read it in the editors that matter, and a
+ * toolbar that guessed would either grey out a command that works or leave a
+ * command live that does nothing. So the caller answers the question it is the
+ * only party that can, on every render, and Prism draws the answer.
+ */
+export type TextFormatCommand = {
+    /**
+     * The caller's own identity for the command.
+     *
+     * Required, and required as a stable string rather than as the label, for the
+     * reason every keyed list in this package says: the caller's own words are
+     * localised, and a toolbar keyed on a localised label remounts a control the
+     * moment the reader changes language, which drops the focus the Component just
+     * took pains to hold.
+     */
+    id: string;
+    /**
+     * The command's accessible name, in the product's own words.
+     *
+     * Required, and a string because a name is a string. Format commands are almost
+     * always icon-only, and a row of icon-only buttons with no names is announced
+     * as "button, button, button", which is three controls nobody can tell apart and
+     * a toolbar whose whole job is that they differ. Write the verb or the format
+     * name in the reader's language: "Bold", "Insert link", "Decrease indent".
+     */
+    label: string;
+    /**
+     * The mark for the command.
+     *
+     * A `ReactNode` and not an icon name, because the icon set is Lucide's and the
+     * vocabulary a product uses for formatting is its own: a CMS that calls the
+     * third row a "quote block" wants a glyph that is not Prism's to choose. Pass an
+     * `svg` or an `img`; it is drawn at the size `Button` gives any child, and it
+     * should be `aria-hidden` because `label` already names the control.
+     */
+    icon?: ReactNode;
+    /**
+     * Whether the command is currently applied, for a command that has an on state.
+     *
+     * Omit it and the command is drawn as a `Button` and announced as a button. Pass
+     * `true` or `false` and it is drawn as a `Toggle` carrying `aria-pressed`, which
+     * is the difference between "bold is available here" and "bold is on right now".
+     * The two are routinely confused, and a toolbar that reports the first as the
+     * second tells a screen reader user their text is bold when it is not, which is
+     * the one claim in a text editor a reader cannot check for themselves.
+     */
+    pressed?: boolean;
+    /**
+     * Whether the command can run against the selection as it stands.
+     *
+     * Required, and a boolean rather than a callback on purpose. A callback would be
+     * read at the moment of the press, which is the moment the selection has already
+     * been disturbed by the press, so the answer would be about a selection that no
+     * longer exists. A boolean read on render is about the selection the reader can
+     * see, which is the one the command will act on.
+     */
+    isEnabled: boolean;
+    /**
+     * Runs the command against the caller's selection.
+     *
+     * Required, and the caller owns everything inside it: reading the selection,
+     * applying the format, and restoring the range afterwards. Prism calls it and
+     * then hands focus back, in that order, for the reason the props below state.
+     */
+    onApply: () => void;
+};
+/**
+ * The props the Text format toolbar accepts.
+ *
+ * A declared interface rather than a forwarded native one: the Component draws a
+ * `toolbar` and its own children, so there is no native element left to forward
+ * to and a forwarded `onKeyDown` would be a second place the arrow-key model
+ * lives.
+ */
+export interface TextFormatToolbarProps {
+    /**
+     * The commands, in the order the arrow keys walk them.
+     *
+     * Required, and the order is the caller's because it is a claim about how often
+     * each command is used: a formatting row where link sits between bold and
+     * italic is one every reader has to learn again. Prism draws no separators and
+     * draws no groups, so an order is the only grouping the row has.
+     */
+    commands: readonly TextFormatCommand[];
+    /**
+     * The toolbar's accessible name.
+     *
+     * Required, and a string because an accessible name is a string. A `toolbar`
+     * role with no name is a landmark a screen reader user walks past twice, and
+     * this row is usually one of several on a page. Write what the commands act on:
+     * "Text formatting", "Formatting for the description".
+     */
+    label: string;
+    /**
+     * Returns the element that holds the selection the commands act on.
+     *
+     * Required, and a function rather than a ref because the Component has to read
+     * it at two moments it cannot predict: after a press, to know whether the reader
+     * is still on the toolbar and therefore whether focus is owed back, and after
+     * the command has run, to send that focus to the element that lost it. A ref
+   * * would be read once, at mount, which is before the caller's editor exists in
+     * most arrangements and stale for the rest of the page's life.
+     *
+     * Return the element that should receive focus: a `contenteditable`, the wrapper
+     * around a third-party editor, the input a markdown source is typed into. Return
+     * `null` and the Component runs the command and leaves focus alone, which is the
+     * right answer for a caller whose commands open something else.
+     */
+    getEditor: () => HTMLElement | null;
+    /** Layout only. Changing a Prism-owned visual property from here is prohibited. */
+    className?: string;
+}
+/**
+ * A row of commands that act on a selection somewhere else on the page.
+ *
+ * **It is a `toolbar` and not a row of buttons, and the role is the Component
+ * rather than a prop.** Prism already owns the other half of this decision in
+ * `DataToolbar`, and it drew the opposite one for a good reason: that row is a
+ * frame, its controls are the caller's, and a `toolbar` role teaches a reader that
+ * the arrow keys move between the things inside it, which is a promise a frame
+ * that mostly holds a search box does not keep. Here the promise is kept, because
+ * every control in the row is drawn by this Component out of the caller's command
+ * data, which means the Component also owns the set the reader walks and the focus
+ * it has to hand back. Taking the role as a prop would be the `DataToolbar`
+ * arrangement with the awkward half removed, and it would let a caller have a row
+ * that claims the arrow-key model without owning anything it could be consistent
+ * about. So the role is not a choice here, and the arrow keys, the single tab stop
+ * and the Home and End keys are part of what this Component is.
+ *
+ * **The enabled state is a state contract of the surface, and that is why this is
+ * not a slot.** The obvious composition is a `DataToolbar` with the caller's
+ * buttons in it, and it is the wrong one for a reason that only shows up once the
+ * selection moves: whether a command is live is a fact about a document state
+ * Prism cannot see, so it changes without any prop of the layout changing and
+ * without a render being caused by anything Prism did. A slot hands that question
+ * to the caller, and the caller answers it in whatever control they happened to
+ * draw, which is how "bold is available" ends up painted as "bold is on" and how a
+ * command that cannot run ends up focusable and silently doing nothing. Here the
+ * question is a required boolean on every command, so it is answered for every
+ * command on every render, and a command that cannot run says so.
+ *
+ * **What Prism cannot verify about the selection is most of it, and it says so
+ * rather than implying otherwise.** This Component never calls
+ * `window.getSelection`. It cannot: the editor may be a `contenteditable`, a
+ * third-party editor with its own document and its own model, an `iframe`, or a
+ * canvas, and in every one of those cases the DOM selection a browser would
+ * report is either absent or a fiction. So three things are the caller's: whether
+ * a command can run, what running it does, and where the range is afterwards. The
+ * Component's entire claim about the selection is the one thing it can honestly
+ * make, which is that a pointer press on a command does not take focus out of the
+ * editor, because focus leaving a `contenteditable` collapses its selection in
+ * several engines and the command would then act on nothing. That is why every
+ * control carries a `mousedown` that prevents the default.
+ *
+ * **A pointer press does not move focus, and a keyboard one has to.** Those are
+ * opposite requirements and the Component answers both, which is the part worth
+ * being explicit about. Preventing the default on `mousedown` keeps the editor's
+ * focus, and therefore its selection, alive; a reader using a mouse never sees a
+ * focus ring on a command, and that is correct, because their focus never left
+ * the text they are editing. A reader using the keyboard reaches the commands with
+ * Tab, which is the one tab stop the `toolbar` role promises, and then their focus
+ * genuinely is on a command, so the Component owes it back.
+ *
+ * **Focus goes back after the command, and only if it is still on the toolbar.**
+ * Order matters: a command that restores its own range does it against whatever
+ * has focus at the time, so the Component sends focus back last and the caller's
+ * range is the last thing standing. And the return is conditional, because a
+ * command that opened a dialog or moved focus into a preview has already put the
+ * reader where they belong, and a Component that pulled focus back from it would
+ * be undoing the caller's own arrangement. Prism's claim stops at the element
+ * `getEditor` returned. It cannot restore the caret's offset, the scroll position
+ * or the direction of the range, and it does not try: a selection is a claim about
+ * the caller's document, and a Component that guessed at one would be the reason a
+ * reader's text was rewritten in a position they did not choose.
+ *
+ * **Unavailable is drawn, not removed, and it is not the native `disabled`.** A
+ * command that cannot run keeps its place in the row and in the arrow-key walk,
+ * carries `aria-disabled`, and refuses the press in its handler. The same argument
+ * `Dropzone` makes: a control that vanishes leaves a keyboard reader with a gap and
+ * no announcement, and a natively disabled one leaves the row with a hole in it
+ * that a reader has to interpret. The cost is that the row is wider than the set
+ * of things a reader can do right now, and the reason a command is unavailable is
+ * the caller's to state beside the editor.
+ *
+ * **It composes `Button` and `Toggle` and does not compose `Tooltip`, and the
+ * refusal has a reason worth recording.** Every command's control is one of those
+ * two, so the metrics, the press feedback, the coarse-pointer floor and the
+ * full-strength ring are Prism's and not re-derived. `Tooltip` cannot join them,
+ * because `TooltipTrigger` renders its own `<button>`: wrapping a command in one
+ * would put a button inside a button, which is the arrangement `Dropzone` refuses
+ * for a file input and for exactly the same reasons. So the name is the
+ * `aria-label` and a caller who wants a phrase beside an icon-only command puts a
+ * `Tooltip` around their own editor control, or names the command in full.
+ *
+ * **It is a client Component**, because it takes focus from one element and gives
+ * it to another, holds the one tab stop the role promises, and takes three
+ * callbacks. None of that is knowable at a server render, and all of it is the
+ * Component's reason to exist. What it costs is a small one, and worth naming: the
+ * Component reads the commands on every render, so a caller who recomputes its
+ * `isEnabled` booleans by walking the document has done that walk on every
+ * keystroke anywhere on the page.
+ */
+declare function TextFormatToolbar({ commands, label, getEditor, className, }: TextFormatToolbarProps): import("react").JSX.Element;
+export { TextFormatToolbar };
+//# sourceMappingURL=text-format-toolbar.d.ts.map

package/dist/components/ui/text-format-toolbar.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"text-format-toolbar.d.ts","sourceRoot":"","sources":["../../../src/components/ui/text-format-toolbar.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAyD,KAAK,SAAS,EAAE,MAAM,OAAO,CAAA;AAM7F;;;;;;;;;GASG;AACH,MAAM,MAAM,iBAAiB,GAAG;IAC9B;;;;;;;;OAQG;IACH,EAAE,EAAE,MAAM,CAAA;IACV;;;;;;;;OAQG;IACH,KAAK,EAAE,MAAM,CAAA;IACb;;;;;;;;OAQG;IACH,IAAI,CAAC,EAAE,SAAS,CAAA;IAChB;;;;;;;;;OASG;IACH,OAAO,CAAC,EAAE,OAAO,CAAA;IACjB;;;;;;;;OAQG;IACH,SAAS,EAAE,OAAO,CAAA;IAClB;;;;;;OAMG;IACH,OAAO,EAAE,MAAM,IAAI,CAAA;CACpB,CAAA;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,sBAAsB;IACrC;;;;;;;OAOG;IACH,QAAQ,EAAE,SAAS,iBAAiB,EAAE,CAAA;IACtC;;;;;;;OAOG;IACH,KAAK,EAAE,MAAM,CAAA;IACb;;;;;;;;;;;;;;OAcG;IACH,SAAS,EAAE,MAAM,WAAW,GAAG,IAAI,CAAA;IACnC,mFAAmF;IACnF,SAAS,CAAC,EAAE,MAAM,CAAA;CACnB;AAcD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAyFG;AACH,iBAAS,iBAAiB,CAAC,EACzB,QAAQ,EACR,KAAK,EACL,SAAS,EACT,SAAS,GACV,EAAE,sBAAsB,+BAmIxB;AAED,OAAO,EAAE,iBAAiB,EAAE,CAAA"}

package/dist/components/ui/text-format-toolbar.js

@@ -0,0 +1,186 @@
+'use client';
+import { jsx as _jsx } from "react/jsx-runtime";
+import { useRef, useState } from 'react';
+import { Button } from './button.js';
+import { Toggle } from './toggle.js';
+import { cn } from '../../lib/utils.js';
+/**
+ * The commands, read back through one root ref for the arrow-key walk and for the
+ * focus handoff.
+ *
+ * The Component's own slot rather than a ref per command, for the same reason
+ * `RepeatableRows` does it: a ref array indexed by position is a second list to
+ * reconcile against the caller's `commands` on every render, and the commands are
+ * the caller's data. A query reaches exactly the set that has to move, which is
+ * the set this Component drew.
+ */
+const COMMAND_SLOT = '[data-slot="text-format-toolbar-command"]';
+/**
+ * A row of commands that act on a selection somewhere else on the page.
+ *
+ * **It is a `toolbar` and not a row of buttons, and the role is the Component
+ * rather than a prop.** Prism already owns the other half of this decision in
+ * `DataToolbar`, and it drew the opposite one for a good reason: that row is a
+ * frame, its controls are the caller's, and a `toolbar` role teaches a reader that
+ * the arrow keys move between the things inside it, which is a promise a frame
+ * that mostly holds a search box does not keep. Here the promise is kept, because
+ * every control in the row is drawn by this Component out of the caller's command
+ * data, which means the Component also owns the set the reader walks and the focus
+ * it has to hand back. Taking the role as a prop would be the `DataToolbar`
+ * arrangement with the awkward half removed, and it would let a caller have a row
+ * that claims the arrow-key model without owning anything it could be consistent
+ * about. So the role is not a choice here, and the arrow keys, the single tab stop
+ * and the Home and End keys are part of what this Component is.
+ *
+ * **The enabled state is a state contract of the surface, and that is why this is
+ * not a slot.** The obvious composition is a `DataToolbar` with the caller's
+ * buttons in it, and it is the wrong one for a reason that only shows up once the
+ * selection moves: whether a command is live is a fact about a document state
+ * Prism cannot see, so it changes without any prop of the layout changing and
+ * without a render being caused by anything Prism did. A slot hands that question
+ * to the caller, and the caller answers it in whatever control they happened to
+ * draw, which is how "bold is available" ends up painted as "bold is on" and how a
+ * command that cannot run ends up focusable and silently doing nothing. Here the
+ * question is a required boolean on every command, so it is answered for every
+ * command on every render, and a command that cannot run says so.
+ *
+ * **What Prism cannot verify about the selection is most of it, and it says so
+ * rather than implying otherwise.** This Component never calls
+ * `window.getSelection`. It cannot: the editor may be a `contenteditable`, a
+ * third-party editor with its own document and its own model, an `iframe`, or a
+ * canvas, and in every one of those cases the DOM selection a browser would
+ * report is either absent or a fiction. So three things are the caller's: whether
+ * a command can run, what running it does, and where the range is afterwards. The
+ * Component's entire claim about the selection is the one thing it can honestly
+ * make, which is that a pointer press on a command does not take focus out of the
+ * editor, because focus leaving a `contenteditable` collapses its selection in
+ * several engines and the command would then act on nothing. That is why every
+ * control carries a `mousedown` that prevents the default.
+ *
+ * **A pointer press does not move focus, and a keyboard one has to.** Those are
+ * opposite requirements and the Component answers both, which is the part worth
+ * being explicit about. Preventing the default on `mousedown` keeps the editor's
+ * focus, and therefore its selection, alive; a reader using a mouse never sees a
+ * focus ring on a command, and that is correct, because their focus never left
+ * the text they are editing. A reader using the keyboard reaches the commands with
+ * Tab, which is the one tab stop the `toolbar` role promises, and then their focus
+ * genuinely is on a command, so the Component owes it back.
+ *
+ * **Focus goes back after the command, and only if it is still on the toolbar.**
+ * Order matters: a command that restores its own range does it against whatever
+ * has focus at the time, so the Component sends focus back last and the caller's
+ * range is the last thing standing. And the return is conditional, because a
+ * command that opened a dialog or moved focus into a preview has already put the
+ * reader where they belong, and a Component that pulled focus back from it would
+ * be undoing the caller's own arrangement. Prism's claim stops at the element
+ * `getEditor` returned. It cannot restore the caret's offset, the scroll position
+ * or the direction of the range, and it does not try: a selection is a claim about
+ * the caller's document, and a Component that guessed at one would be the reason a
+ * reader's text was rewritten in a position they did not choose.
+ *
+ * **Unavailable is drawn, not removed, and it is not the native `disabled`.** A
+ * command that cannot run keeps its place in the row and in the arrow-key walk,
+ * carries `aria-disabled`, and refuses the press in its handler. The same argument
+ * `Dropzone` makes: a control that vanishes leaves a keyboard reader with a gap and
+ * no announcement, and a natively disabled one leaves the row with a hole in it
+ * that a reader has to interpret. The cost is that the row is wider than the set
+ * of things a reader can do right now, and the reason a command is unavailable is
+ * the caller's to state beside the editor.
+ *
+ * **It composes `Button` and `Toggle` and does not compose `Tooltip`, and the
+ * refusal has a reason worth recording.** Every command's control is one of those
+ * two, so the metrics, the press feedback, the coarse-pointer floor and the
+ * full-strength ring are Prism's and not re-derived. `Tooltip` cannot join them,
+ * because `TooltipTrigger` renders its own `<button>`: wrapping a command in one
+ * would put a button inside a button, which is the arrangement `Dropzone` refuses
+ * for a file input and for exactly the same reasons. So the name is the
+ * `aria-label` and a caller who wants a phrase beside an icon-only command puts a
+ * `Tooltip` around their own editor control, or names the command in full.
+ *
+ * **It is a client Component**, because it takes focus from one element and gives
+ * it to another, holds the one tab stop the role promises, and takes three
+ * callbacks. None of that is knowable at a server render, and all of it is the
+ * Component's reason to exist. What it costs is a small one, and worth naming: the
+ * Component reads the commands on every render, so a caller who recomputes its
+ * `isEnabled` booleans by walking the document has done that walk on every
+ * keystroke anywhere on the page.
+ */
+function TextFormatToolbar({ commands, label, getEditor, className, }) {
+    const rootRef = useRef(null);
+    // The one tab stop the `toolbar` role promises, held as a position so a caller
+    // who reorders the commands does not strand the reader on a command that moved.
+    const [active, setActive] = useState(0);
+    // The one tab stop the `toolbar` role promises, clamped to the row. A caller who
+    // removes commands can leave the remembered position past the end, and a
+    // toolbar with no tab stop is a toolbar a keyboard reader has to step over.
+    const stop = active < commands.length ? active : 0;
+    const focusCommand = (index) => {
+        const count = commands.length;
+        if (count === 0)
+            return;
+        // Wrapping is the toolbar model rather than the list model: a reader who
+        // arrows off the right end expects the row to continue, because a row that
+        // stops is a row they have to Tab out of and back into to reach the first
+        // command again.
+        const next = ((index % count) + count) % count;
+        setActive(next);
+        const command = rootRef.current
+            ?.querySelectorAll(COMMAND_SLOT)
+            .item(next);
+        command?.focus();
+    };
+    const onKeyDown = (event) => {
+        switch (event.key) {
+            case 'ArrowRight':
+                event.preventDefault();
+                focusCommand(active + 1);
+                return;
+            case 'ArrowLeft':
+                event.preventDefault();
+                focusCommand(active - 1);
+                return;
+            case 'Home':
+                event.preventDefault();
+                focusCommand(0);
+                return;
+            case 'End':
+                event.preventDefault();
+                focusCommand(commands.length - 1);
+                return;
+            default:
+        }
+    };
+    const onPointerDown = (event) => {
+        // The one line that keeps a format toolbar working. Focus leaving an editor
+        // collapses its selection in several engines, so a press that moved focus
+        // would leave the command acting on a selection the reader can no longer see.
+        // The control still receives the press, still draws its active surface, and
+        // still fires its click; only the focus move is declined.
+        event.preventDefault();
+    };
+    const apply = (command) => {
+        if (!command.isEnabled)
+            return;
+        command.onApply();
+        // Read after the command, not before: a command that opened something has
+        // already moved the reader there, and pulling focus back from it would undo
+        // the caller's own arrangement. A reader still on the toolbar after the
+        // command has run is a reader who got there with the keyboard, and the editor
+        // is where they were working.
+        const root = rootRef.current;
+        if (root === null || !root.contains(document.activeElement))
+            return;
+        getEditor()?.focus();
+    };
+    return (_jsx("div", { ref: rootRef, "data-slot": "text-format-toolbar", role: "toolbar", "aria-label": label, "aria-orientation": "horizontal", onKeyDown: onKeyDown, className: cn('bg-card flex w-full items-center gap-1 rounded-md border p-1', className), children: commands.map((command, index) => {
+            const unavailable = !command.isEnabled;
+            return (_jsx("span", { "data-slot": "text-format-toolbar-item", "data-unavailable": unavailable || undefined, 
+                // The unavailable surface is on the wrapper rather than on the
+                // control, because `Button` and `Toggle` style the native `disabled`
+                // attribute and this Component does not set it. The dimming is Prism's
+                // and the control keeps its own focus ring, its press feedback and its
+                // place in the arrow-key walk.
+                className: cn('inline-flex', unavailable && 'opacity-50'), children: command.pressed === undefined ? (_jsx(Button, { "data-slot": "text-format-toolbar-command", type: "button", variant: "ghost", size: "icon", tabIndex: index === stop ? 0 : -1, "aria-label": command.label, "aria-disabled": unavailable || undefined, onMouseDown: onPointerDown, onClick: () => apply(command), children: command.icon })) : (_jsx(Toggle, { "data-slot": "text-format-toolbar-command", type: "button", size: "sm", tabIndex: index === stop ? 0 : -1, "aria-label": command.label, "aria-disabled": unavailable || undefined, pressed: command.pressed, onMouseDown: onPointerDown, onClick: () => apply(command), children: command.icon })) }, command.id));
+        }) }));
+}
+export { TextFormatToolbar };

package/dist/components/ui/timeline.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"timeline.d.ts","sourceRoot":"","sources":["../../../src/components/ui/timeline.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AAItD;;;;;;;;;;;;;GAaG;AACH,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,SAAS,GAAG,MAAM,GAAG,QAAQ,CAAA;AAErE,0BAA0B;AAC1B,MAAM,MAAM,aAAa,GAAG;IAC1B;;;;;;OAMG;IACH,EAAE,EAAE,MAAM,CAAA;IACV,sCAAsC;IACtC,KAAK,EAAE,MAAM,CAAA;IACb;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,8CAA8C;IAC9C,KAAK,CAAC,EAAE,aAAa,CAAA;IACrB,8EAA8E;IAC9E,QAAQ,CAAC,EAAE,SAAS,CAAA;CACrB,CAAA;AAED,sCAAsC;AACtC,MAAM,WAAW,aAAc,SAAQ,IAAI,CAAC,cAAc,CAAC,IAAI,CAAC,EAAE,UAAU,CAAC;IAC3E;;;;;;OAMG;IACH,OAAO,EAAE,SAAS,aAAa,EAAE,CAAA;IACjC;;;;;OAKG;IACH,KAAK,EAAE,MAAM,CAAA;IACb;;;;;;OAMG;IACH,MAAM,CAAC,EAAE,CAAC,EAAE,EAAE,MAAM,KAAK,MAAM,CAAA;IAC/B,mBAAmB;IACnB,SAAS,CAAC,EAAE,MAAM,CAAA;IAClB;;;;;OAKG;IACH,KAAK,CAAC,EAAE,SAAS,CAAA;CAClB;AAgDD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,iBAAS,QAAQ,CAAC,EAChB,OAAO,EACP,KAAK,EACL,MAAsB,EACtB,SAAS,EACT,KAAK,EACL,GAAG,KAAK,EACT,EAAE,aAAa,+BAkIf;AAED,OAAO,EAAE,QAAQ,EAAE,CAAA"}
+{"version":3,"file":"timeline.d.ts","sourceRoot":"","sources":["../../../src/components/ui/timeline.tsx"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,cAAc,EAAE,SAAS,EAAE,MAAM,OAAO,CAAA;AAItD;;;;;;;;;;;;;GAaG;AACH,MAAM,MAAM,aAAa,GAAG,SAAS,GAAG,SAAS,GAAG,MAAM,GAAG,QAAQ,CAAA;AAErE,0BAA0B;AAC1B,MAAM,MAAM,aAAa,GAAG;IAC1B;;;;;;OAMG;IACH,EAAE,EAAE,MAAM,CAAA;IACV,sCAAsC;IACtC,KAAK,EAAE,MAAM,CAAA;IACb;;;;;OAKG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,8CAA8C;IAC9C,KAAK,CAAC,EAAE,aAAa,CAAA;IACrB,8EAA8E;IAC9E,QAAQ,CAAC,EAAE,SAAS,CAAA;CACrB,CAAA;AAED,sCAAsC;AACtC,MAAM,WAAW,aAAc,SAAQ,IAAI,CAAC,cAAc,CAAC,IAAI,CAAC,EAAE,UAAU,CAAC;IAC3E;;;;;;OAMG;IACH,OAAO,EAAE,SAAS,aAAa,EAAE,CAAA;IACjC;;;;;OAKG;IACH,KAAK,EAAE,MAAM,CAAA;IACb;;;;;;OAMG;IACH,MAAM,CAAC,EAAE,CAAC,EAAE,EAAE,MAAM,KAAK,MAAM,CAAA;IAC/B,mBAAmB;IACnB,SAAS,CAAC,EAAE,MAAM,CAAA;IAClB;;;;;OAKG;IACH,KAAK,CAAC,EAAE,SAAS,CAAA;CAClB;AAgDD;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,iBAAS,QAAQ,CAAC,EAChB,OAAO,EACP,KAAK,EACL,MAAsB,EACtB,SAAS,EACT,KAAK,EACL,GAAG,KAAK,EACT,EAAE,aAAa,+BA2If;AAED,OAAO,EAAE,QAAQ,EAAE,CAAA"}

package/dist/components/ui/timeline.js

@@ -98,7 +98,16 @@ function Timeline({ entries, label, format = defaultFormat, className, empty, ..
             return (_jsxs("li", { "data-slot": "timeline-entry", "data-state": state, className: "grid grid-cols-[auto_1fr] gap-x-3", children: [_jsxs("div", { "data-slot": "timeline-rail", "aria-hidden": "true", className: "flex flex-col items-center", children: [_jsx("span", { "data-slot": "timeline-mark", className: cn('mt-1.5 size-2 shrink-0 rounded-full border-2', STATE_MARK[state], 
                                 // A running step is the one that is still moving, and a ring that
                                 // pulses is the only motion in the Component. It is state
-                                // feedback, not decoration: it stops when the step stops.
+                                // feedback, not decoration: it stops when the step stops. It is
+                                // not guarded here because the stylesheet stops it: the
+                                // reduced-motion rule at the foot of `packages/ui/src/styles.css`
+                                // sets `animation: none` on the universal selector, and an
+                                // `animate-pulse` outside the seven classes that rule used to name
+                                // is the second unbounded loop this Component was shipping. The
+                                // mark is `aria-hidden` inside a `data-state` rail and the entry's
+                                // own words carry the state, so a reader with the setting on reads
+                                // "Deploying" and watches a still ring, which is the same sentence
+                                // with the emphasis removed.
                                 state === 'running' && 'animate-pulse') }), isLast ? null : _jsx("span", { "data-slot": "timeline-spine", className: "bg-border w-px flex-1" })] }), _jsxs("div", { className: cn(
                         // The last entry has nothing under it, so its bottom padding is
                         // dropped rather than leaving a gap the reader reads as a

package/dist/components/ui/toast.d.ts

@@ -72,6 +72,12 @@ export interface ToastProps extends Omit<ComponentProps<'div'>, 'children' | 'ti
      * caller who expects the toast to remove itself will write a no-op and leave
      * a toast parked on the page forever.
      *
+     * **Called exactly once, and called whether or not the fade ran.** It fires at
+     * the end of the leave when there is a leave to watch, and on the same commit
+     * when there is not, so a consumer whose own stylesheet kills transitions with
+     * `transition: none` gets a toast that goes rather than a toast stuck in
+     * `data-phase="leaving"`.
+     *
      * **Omitting it makes the toast permanent, and that is deliberate.** Without a
      * handoff there is nobody to take the toast off the page, so a clock with
      * nothing to fire and a dismiss control with nothing to do would both be
@@ -190,16 +196,32 @@ export interface ToastProps extends Omit<ComponentProps<'div'>, 'children' | 'ti
  * have.
  *
  * **It never removes its own transition, and the reason is the caller's
- * unmount.** The exit hands over on the end of the root's own opacity
- * transition, so under reduced motion the fade is *shortened* rather than
- * removed and the handoff still happens. Removing the fade there would have
- * needed this Component to read the media query and hand over at once instead,
- * which would be the same rule written twice: once in the stylesheet and once in
- * TypeScript, free to disagree the day the motion policy is retuned. Leaving
- * the fade in and shortening it keeps the decision in one place, and it is the
- * same choice `DESIGN.md` states for the package: motion is state feedback,
- * shortened rather than removed under reduced motion. The travel is the part
- * that is movement, so that is the part `motion-safe:` guards.
+ * unmount.** The enter and the leave are shortened rather than removed under
+ * reduced motion, and shortening them there would have needed this Component to
+ * read the media query and hand over at once instead, which would be the same
+ * rule written twice: once in the stylesheet and once in TypeScript, free to
+ * disagree the day the motion policy is retuned. It does not read it. It also
+ * does not guard the travel at the call site any more, because
+ * `packages/ui/src/styles.css` stops every transition and every animation under
+ * `prefers-reduced-motion` in one unlayered rule, and a `motion-safe:` beside an
+ * unguarded `transition-[opacity,transform]` was the shape `RangeField` shipped:
+ * a guard that adds a rule and therefore cannot remove one. The rise is movement
+ * and it is stopped, the fade is stopped with everything else, and the exit is
+ * asked about rather than assumed, which is what the paragraph below is for.
+ *
+ * **The leave is handed over whether or not the fade runs, and that is the
+ * contract `styles.css` states for the whole package.** `packages/ui/src/styles.css`
+ * says there is no state anywhere in this system whose exit depends on an animation
+ * running to completion, and this Component is where that was not true: the exit
+ * waited on `transitionend` and nothing else. A consumer's global
+ * `transition: none` broke it first, and the reduced-motion block at the foot of
+ * that stylesheet breaks it now that it names transitions as well as animations, so
+ * a toast stranded in `leaving` was and would be visible, undismissable and still
+ * inside a live region. So the exit asks the browser what is actually running on
+ * the root rather than waiting for an event that a killed transition never sends:
+ * it waits for the fade when there is a fade, it hands over on the same commit when
+ * there is not, and `onDismiss` is called exactly once either way. This Component is
+ * the reason the one unlayered rule above it is safe to ship.
  *
  * **It is a client Component** because it holds a clock, runs effects, and
  * attaches three handlers. The clock is a single `setTimeout` whose

package/dist/components/ui/toast.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"toast.d.ts","sourceRoot":"","sources":["../../../src/components/ui/toast.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAO,KAAK,YAAY,EAAE,MAAM,0BAA0B,CAAA;AAEjE,OAAO,EAA4C,KAAK,cAAc,EAAsB,KAAK,SAAS,EAAE,MAAM,OAAO,CAAA;AAIzH;;;;;;;;;;GAUG;AACH,QAAA,MAAM,aAAa;;8EAsBlB,CAAA;AAaD;;;;;;;GAOG;AACH,MAAM,WAAW,UACf,SAAQ,IAAI,CAAC,cAAc,CAAC,KAAK,CAAC,EAAE,UAAU,GAAG,OAAO,CAAC,EACvD,YAAY,CAAC,OAAO,aAAa,CAAC;IACpC;;;;;;;;;;;;;;;;;OAiBG;IACH,KAAK,CAAC,EAAE,SAAS,CAAA;IACjB;;;;;;OAMG;IACH,WAAW,CAAC,EAAE,SAAS,CAAA;IACvB;;;;;;;;;;OAUG;IACH,MAAM,CAAC,EAAE,SAAS,CAAA;IAClB;;;;;;;;;;;;;;;;;;OAkBG;IACH,SAAS,CAAC,EAAE,MAAM,IAAI,CAAA;IACtB;;;;;;;;;;;;;;;;;OAiBG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;;;;;;;OAUG;IACH,UAAU,EAAE,MAAM,CAAA;IAClB;;;;;;;;;;;;;;;OAeG;IACH,eAAe,CAAC,EAAE,OAAO,CAAA;IACzB;;;;;;;;OAQG;IACH,MAAM,CAAC,EAAE,OAAO,CAAA;CACjB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwEG;AACH,iBAAS,KAAK,CAAC,EACb,SAAS,EACT,OAAO,EACP,KAAK,EACL,WAAW,EACX,MAAM,EACN,SAAS,EACT,QAAe,EACf,UAAU,EACV,eAAsB,EACtB,MAAc,EACd,GAAG,KAAK,EACT,EAAE,UAAU,+BA4NZ;AAED,OAAO,EAAE,KAAK,EAAE,CAAA"}
+{"version":3,"file":"toast.d.ts","sourceRoot":"","sources":["../../../src/components/ui/toast.tsx"],"names":[],"mappings":"AAEA,OAAO,EAAO,KAAK,YAAY,EAAE,MAAM,0BAA0B,CAAA;AAEjE,OAAO,EAA4C,KAAK,cAAc,EAAsB,KAAK,SAAS,EAAE,MAAM,OAAO,CAAA;AAIzH;;;;;;;;;;GAUG;AACH,QAAA,MAAM,aAAa;;8EAsBlB,CAAA;AAmCD;;;;;;;GAOG;AACH,MAAM,WAAW,UACf,SAAQ,IAAI,CAAC,cAAc,CAAC,KAAK,CAAC,EAAE,UAAU,GAAG,OAAO,CAAC,EACvD,YAAY,CAAC,OAAO,aAAa,CAAC;IACpC;;;;;;;;;;;;;;;;;OAiBG;IACH,KAAK,CAAC,EAAE,SAAS,CAAA;IACjB;;;;;;OAMG;IACH,WAAW,CAAC,EAAE,SAAS,CAAA;IACvB;;;;;;;;;;OAUG;IACH,MAAM,CAAC,EAAE,SAAS,CAAA;IAClB;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;IACH,SAAS,CAAC,EAAE,MAAM,IAAI,CAAA;IACtB;;;;;;;;;;;;;;;;;OAiBG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB;;;;;;;;;;OAUG;IACH,UAAU,EAAE,MAAM,CAAA;IAClB;;;;;;;;;;;;;;;OAeG;IACH,eAAe,CAAC,EAAE,OAAO,CAAA;IACzB;;;;;;;;OAQG;IACH,MAAM,CAAC,EAAE,OAAO,CAAA;CACjB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwFG;AACH,iBAAS,KAAK,CAAC,EACb,SAAS,EACT,OAAO,EACP,KAAK,EACL,WAAW,EACX,MAAM,EACN,SAAS,EACT,QAAe,EACf,UAAU,EACV,eAAsB,EACtB,MAAc,EACd,GAAG,KAAK,EACT,EAAE,UAAU,+BA8RZ;AAED,OAAO,EAAE,KAAK,EAAE,CAAA"}