@allxsmith/bestax-bulma 5.26.4 → 5.26.6

package/dist/types/form/Autocomplete.d.ts

@@ -37,7 +37,12 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     placeholder?: string;
     /** Object property to use as the display field. */
     field?: string;
-    /** Whether to show a clear button. */
+    /**
+     * Whether to show a clear button while the input holds a value.
+     * It hides while the input is disabled, and gives way to a loading
+     * spinner at the same right edge: the one `loading` draws, or that of a
+     * `Control` with `isLoading` around the Autocomplete.
+     */
     clearable?: boolean;
     /** Open dropdown when input is focused. */
     openOnFocus?: boolean;

package/dist/types/form/DateInput.d.ts

@@ -5,9 +5,12 @@ import { DateInputBaseProps } from './DateInputBase.js';
 /**
  * Props for the DateInput convenience wrapper. Extends `DateInputBaseProps`
  * with Field-level (label, horizontal) and Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -52,7 +55,8 @@ export interface DateInputProps extends DateInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */

package/dist/types/form/DateTimeInput.d.ts

@@ -5,9 +5,12 @@ import { DateTimeInputBaseProps } from './DateTimeInputBase.js';
 /**
  * Props for the DateTimeInput convenience wrapper. Extends
  * `DateTimeInputBaseProps` with Field-level and Control-level props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -50,7 +53,8 @@ export interface DateTimeInputProps extends DateTimeInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */

package/dist/types/form/FormContext.d.ts

@@ -1,4 +1,5 @@
 import React from 'react';
+import type { ControlBaseProps } from './Control.js';
 /**
  * Hook to detect if the component is inside a Field wrapper.
  * Form components use this to skip rendering their own Field.
@@ -43,6 +44,52 @@ interface OwnFieldOptions extends FieldShapingProps {
  * Internal; not part of the public API.
  */
 export declare const rendersOwnField: (component: string, options: OwnFieldOptions) => boolean;
+/** The props a convenience form wrapper hands its own `Control`. Internal. */
+export interface ControlLevelProps {
+    /** Shows the `Control`'s loading spinner. */
+    isLoading?: boolean;
+    /** The `Control`'s left icon. */
+    iconLeft?: ControlBaseProps['iconLeft'];
+    /** Shortcut for the left icon's name. */
+    iconLeftName?: string;
+    /** Shortcut for the left icon's size. */
+    iconLeftSize?: ControlBaseProps['iconLeftSize'];
+    /** The `Control`'s right icon. */
+    iconRight?: ControlBaseProps['iconRight'];
+    /** Shortcut for the right icon's name. */
+    iconRightName?: string;
+    /** Shortcut for the right icon's size. */
+    iconRightSize?: ControlBaseProps['iconRightSize'];
+    /** Reserves the `Control`'s left icon space. */
+    hasIconsLeft?: boolean;
+    /** Reserves the `Control`'s right icon space. */
+    hasIconsRight?: boolean;
+    /** Expands the `Control`. */
+    isExpanded?: boolean;
+    /** Set on the `Control` as its `size`. */
+    controlSize?: ControlBaseProps['size'];
+    /** Set on the `Control` as its class. */
+    controlClassName?: string;
+}
+interface OwnControlOptions extends ControlLevelProps {
+    /** `useInsideControl()` as the wrapper read it. */
+    insideControl: boolean;
+    /** A picker's `inline`, which renders no `Control` inside one or out. */
+    inline?: boolean;
+}
+/**
+ * Whether a convenience form wrapper renders a `Control` of its own (#921):
+ * only outside one. Inside a `Control` it renders none, so the props it
+ * would have handed its own do nothing there, and it warns in development,
+ * naming them and saying to set them on that `Control`. An `inline` picker
+ * renders none in either place, so it drops them inside a `Control` or not,
+ * and its warning says so without pointing at a `Control`. A wrapper passes
+ * only the props it hands its own `Control`, as the caller gave them, so a
+ * default the wrapper fills in itself never warns. A prop counts when it is
+ * truthy, since a falsy one would change nothing on a `Control` either.
+ * Internal; not part of the public API.
+ */
+export declare const rendersOwnControl: (component: string, options: OwnControlOptions) => boolean;
 /**
  * The id a labeled Field wants its single composed control to adopt (#495).
  * `undefined` outside a Field, in unlabeled/grouped/addons Fields, or when the

package/dist/types/form/Input.d.ts

@@ -8,9 +8,10 @@ import { InputBaseProps } from './InputBase.js';
  * Composes Field, Control, and Input into a single convenience component.
  * Supports all Input props, plus Field-level (label, horizontal) and
  * Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types/form/Numberinput.d.ts

@@ -45,7 +45,14 @@ export interface NumberinputProps extends Omit<React.InputHTMLAttributes<HTMLInp
     controlsRounded?: boolean;
     /** Uses compact button spacing. */
     compact?: boolean;
-    /** Removes button borders and background. */
+    /**
+     * Renders the plusminus controls without a `.field` row of their own, so
+     * they join the row of a `Field` with `hasAddons` or `grouped` they sit
+     * in. On by default inside a `Field`, unless a `Control` is anywhere above
+     * it: a `Control` stacks its children, so there the controls keep their
+     * own row.
+     * @defaultValue auto
+     */
     bare?: boolean;
     /** Style variant for the control buttons. */
     variant?: NumberinputVariant;
@@ -57,6 +64,9 @@ export interface NumberinputProps extends Omit<React.InputHTMLAttributes<HTMLInp
      * Shows a loading spinner on the input's control.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
+     * Use this rather than `isLoading` on a `Control` around the Numberinput:
+     * that spinner sits at the `Control`'s right edge, on top of whichever
+     * button is there, while this one stays inside the input.
      */
     isLoading?: boolean;
     /** Enables exponential step increments when holding buttons. */

package/dist/types/form/Select.d.ts

@@ -8,9 +8,10 @@ import { SelectBaseProps } from './SelectBase.js';
  * Composes Field, Control, and SelectBase into a single convenience component.
  * Supports all SelectBase props, plus Field-level (label, horizontal) and
  * Control-level (icons) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types/form/TextArea.d.ts

@@ -8,9 +8,10 @@ import { TextAreaBaseProps } from './TextAreaBase.js';
  * Composes Field, Control, and TextAreaBase into a single convenience component.
  * Supports all TextAreaBase props, plus Field-level (label, horizontal) and
  * Control-level (loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types/form/TimeInput.d.ts

@@ -5,9 +5,12 @@ import { TimeInputBaseProps } from './TimeInputBase.js';
 /**
  * Props for the TimeInput convenience wrapper. Extends `TimeInputBaseProps`
  * with Field-level (label, horizontal) and Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -52,7 +55,8 @@ export interface TimeInputProps extends TimeInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */

package/dist/types/form/_pickerInternals/Calendar.d.ts

@@ -1,9 +1,8 @@
 import React from 'react';
-import { DateGranularity, DayOfWeek, PickerLabels } from './pickerTypes.js';
-export interface CalendarProps {
-    value: Date | null;
+import { DateGranularity, DateRangeValue, DayOfWeek, PickerLabels } from './pickerTypes.js';
+/** What every calendar takes, whichever way it picks. */
+interface CalendarBaseProps {
     focusedDate: Date;
-    onSelect: (d: Date) => void;
     onFocusedDateChange: (d: Date) => void;
     /**
      * Earliest selectable date. One before year 1, or none, counts as the start
@@ -47,6 +46,48 @@ export interface CalendarProps {
      */
     granularity?: DateGranularity;
 }
+/** A calendar that picks one day, month or year. */
+interface CalendarSingleProps {
+    /** The selected date. */
+    value: Date | null;
+    /** Called with a picked date, or the first day of a picked period. */
+    onSelect: (d: Date) => void;
+    range?: never;
+    onRangeSelect?: never;
+    allowDisabledInRange?: never;
+}
+/** A calendar that picks a range of days. */
+interface CalendarRangeProps {
+    /**
+     * The committed range, start first, which turns on range mode. The day grid
+     * then picks two days: the first pick marks a start inside the calendar and
+     * commits nothing, and the second calls `onRangeSelect` with both ends. A
+     * pick that cannot end the range starts a new one instead: one before the
+     * start, or one past a disabled day unless `allowDisabledInRange` is set.
+     * While a start is pending the grid previews the range to the hovered day,
+     * or to the focused day, and hides the committed one. A range with a start
+     * and no end opens with that start pending. Escape takes back a pending pick
+     * and stops there, so a popover around the calendar stays open; a pending
+     * start that came from `range` is not a pick, and Escape goes on.
+     */
+    range: DateRangeValue;
+    /** Called with both ends once the second day is picked. */
+    onRangeSelect: (start: Date, end: Date) => void;
+    /**
+     * Let a range include days that `shouldDisableDate` or `unselectableDates`
+     * disable. Its ends can still not be such days.
+     */
+    allowDisabledInRange?: boolean;
+    /** Only the day grid picks a range. */
+    granularity?: 'day';
+    value?: never;
+    onSelect?: never;
+}
+/**
+ * The calendar picks one date through `value` and `onSelect`, or a range
+ * through `range` and `onRangeSelect`, and its props take exactly one pair.
+ */
+export type CalendarProps = CalendarBaseProps & (CalendarSingleProps | CalendarRangeProps);
 /**
  * Selects the calendar's focused cell, the one tab stop of whichever grid or
  * year list is on show, for a popover to put focus on as it opens. It runs

package/dist/types/form/_pickerInternals/dateUtils.d.ts

@@ -60,6 +60,23 @@ export declare function isDayUnselectable(d: Date, c: DayConstraints): boolean;
  * of 3pm on a month's last day leaves that day, and so its month, selectable.
  */
 export declare function isPeriodUnselectable(d: Date, granularity: DateGranularity, c: DayConstraints): boolean;
+/**
+ * The most days {@link canCloseRange} walks between a range's ends, about
+ * eleven years. A span it would have to walk further is refused, so the check
+ * stays cheap enough to run on every pointer move over the calendar.
+ */
+export declare const RANGE_WALK_LIMIT = 4000;
+/**
+ * Whether `end` can close a range that opens on `start`: it falls on `start`'s
+ * day or later, and, unless `allowDisabled`, no day between the two is one
+ * that `shouldDisableDate` or `unselectableDates` disables. Checking that
+ * walks the days between, so with either rule set and `allowDisabled` off,
+ * an `end` more than {@link RANGE_WALK_LIMIT} days after `start` is refused.
+ * The ends' own constraints, `min` and `max` among them, are the caller's to
+ * check. Bounds can't fall between two days inside them, so they are not
+ * walked.
+ */
+export declare function canCloseRange(start: Date, end: Date, c: DayConstraints, allowDisabled?: boolean): boolean;
 export declare function addDays(d: Date, n: number): Date;
 export declare function addMonths(d: Date, n: number): Date;
 export declare function addYears(d: Date, n: number): Date;

package/dist/types/form/_pickerInternals/pickerTypes.d.ts

@@ -3,6 +3,11 @@ export type HourFormat = '12' | '24';
 export type DayOfWeek = 0 | 1 | 2 | 3 | 4 | 5 | 6;
 /** The unit a date picker selects: a day, a month or a year. */
 export type DateGranularity = 'day' | 'month' | 'year';
+/**
+ * A range of days, start first. Either end may be `null` while the range is
+ * half filled, and `[null, null]` is empty.
+ */
+export type DateRangeValue = [Date | null, Date | null];
 /**
  * Translatable strings used across all four pickers. Pass via the `labels`
  * prop to override defaults; consumers manage their own locale-driven mapping.
@@ -19,6 +24,15 @@ export interface PickerLabels {
     chooseMonth?: string;
     /** Launcher, popover and year list name when the picker selects a year. */
     chooseYear?: string;
+    /** Range picking: names the start of a range, in the calendar and the field. */
+    rangeStart?: string;
+    /** Range picking: names the end of a range, in the calendar and the field. */
+    rangeEnd?: string;
+    /**
+     * Range picking: describes the day a pending range would end on, the one
+     * the pointer or the keyboard is on, until it is picked.
+     */
+    rangePreviewEnd?: string;
     hours?: string;
     minutes?: string;
     seconds?: string;

package/dist/types/helpers/statusRegion.d.ts

@@ -13,6 +13,7 @@ export declare const announceDelay = 100;
  * again.
  */
 export declare const announcementLifetime = 1000;
+export declare const visuallyHidden: React.CSSProperties;
 /**
  * Reads an element out roughly the way a screen reader would: its text, with
  * an element's `aria-label`, or an image's `alt`, standing in for what's

package/dist/types-cjs/form/Autocomplete.d.ts

@@ -37,7 +37,12 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     placeholder?: string;
     /** Object property to use as the display field. */
     field?: string;
-    /** Whether to show a clear button. */
+    /**
+     * Whether to show a clear button while the input holds a value.
+     * It hides while the input is disabled, and gives way to a loading
+     * spinner at the same right edge: the one `loading` draws, or that of a
+     * `Control` with `isLoading` around the Autocomplete.
+     */
     clearable?: boolean;
     /** Open dropdown when input is focused. */
     openOnFocus?: boolean;

package/dist/types-cjs/form/DateInput.d.ts

@@ -5,9 +5,12 @@ import { DateInputBaseProps } from './DateInputBase.js';
 /**
  * Props for the DateInput convenience wrapper. Extends `DateInputBaseProps`
  * with Field-level (label, horizontal) and Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -52,7 +55,8 @@ export interface DateInputProps extends DateInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */

package/dist/types-cjs/form/DateTimeInput.d.ts

@@ -5,9 +5,12 @@ import { DateTimeInputBaseProps } from './DateTimeInputBase.js';
 /**
  * Props for the DateTimeInput convenience wrapper. Extends
  * `DateTimeInputBaseProps` with Field-level and Control-level props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -50,7 +53,8 @@ export interface DateTimeInputProps extends DateTimeInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */

package/dist/types-cjs/form/FormContext.d.ts

@@ -1,4 +1,5 @@
 import React from 'react';
+import type { ControlBaseProps } from './Control.js';
 /**
  * Hook to detect if the component is inside a Field wrapper.
  * Form components use this to skip rendering their own Field.
@@ -43,6 +44,52 @@ interface OwnFieldOptions extends FieldShapingProps {
  * Internal; not part of the public API.
  */
 export declare const rendersOwnField: (component: string, options: OwnFieldOptions) => boolean;
+/** The props a convenience form wrapper hands its own `Control`. Internal. */
+export interface ControlLevelProps {
+    /** Shows the `Control`'s loading spinner. */
+    isLoading?: boolean;
+    /** The `Control`'s left icon. */
+    iconLeft?: ControlBaseProps['iconLeft'];
+    /** Shortcut for the left icon's name. */
+    iconLeftName?: string;
+    /** Shortcut for the left icon's size. */
+    iconLeftSize?: ControlBaseProps['iconLeftSize'];
+    /** The `Control`'s right icon. */
+    iconRight?: ControlBaseProps['iconRight'];
+    /** Shortcut for the right icon's name. */
+    iconRightName?: string;
+    /** Shortcut for the right icon's size. */
+    iconRightSize?: ControlBaseProps['iconRightSize'];
+    /** Reserves the `Control`'s left icon space. */
+    hasIconsLeft?: boolean;
+    /** Reserves the `Control`'s right icon space. */
+    hasIconsRight?: boolean;
+    /** Expands the `Control`. */
+    isExpanded?: boolean;
+    /** Set on the `Control` as its `size`. */
+    controlSize?: ControlBaseProps['size'];
+    /** Set on the `Control` as its class. */
+    controlClassName?: string;
+}
+interface OwnControlOptions extends ControlLevelProps {
+    /** `useInsideControl()` as the wrapper read it. */
+    insideControl: boolean;
+    /** A picker's `inline`, which renders no `Control` inside one or out. */
+    inline?: boolean;
+}
+/**
+ * Whether a convenience form wrapper renders a `Control` of its own (#921):
+ * only outside one. Inside a `Control` it renders none, so the props it
+ * would have handed its own do nothing there, and it warns in development,
+ * naming them and saying to set them on that `Control`. An `inline` picker
+ * renders none in either place, so it drops them inside a `Control` or not,
+ * and its warning says so without pointing at a `Control`. A wrapper passes
+ * only the props it hands its own `Control`, as the caller gave them, so a
+ * default the wrapper fills in itself never warns. A prop counts when it is
+ * truthy, since a falsy one would change nothing on a `Control` either.
+ * Internal; not part of the public API.
+ */
+export declare const rendersOwnControl: (component: string, options: OwnControlOptions) => boolean;
 /**
  * The id a labeled Field wants its single composed control to adopt (#495).
  * `undefined` outside a Field, in unlabeled/grouped/addons Fields, or when the

package/dist/types-cjs/form/Input.d.ts

@@ -8,9 +8,10 @@ import { InputBaseProps } from './InputBase.js';
  * Composes Field, Control, and Input into a single convenience component.
  * Supports all Input props, plus Field-level (label, horizontal) and
  * Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types-cjs/form/Numberinput.d.ts

@@ -45,7 +45,14 @@ export interface NumberinputProps extends Omit<React.InputHTMLAttributes<HTMLInp
     controlsRounded?: boolean;
     /** Uses compact button spacing. */
     compact?: boolean;
-    /** Removes button borders and background. */
+    /**
+     * Renders the plusminus controls without a `.field` row of their own, so
+     * they join the row of a `Field` with `hasAddons` or `grouped` they sit
+     * in. On by default inside a `Field`, unless a `Control` is anywhere above
+     * it: a `Control` stacks its children, so there the controls keep their
+     * own row.
+     * @defaultValue auto
+     */
     bare?: boolean;
     /** Style variant for the control buttons. */
     variant?: NumberinputVariant;
@@ -57,6 +64,9 @@ export interface NumberinputProps extends Omit<React.InputHTMLAttributes<HTMLInp
      * Shows a loading spinner on the input's control.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
+     * Use this rather than `isLoading` on a `Control` around the Numberinput:
+     * that spinner sits at the `Control`'s right edge, on top of whichever
+     * button is there, while this one stays inside the input.
      */
     isLoading?: boolean;
     /** Enables exponential step increments when holding buttons. */

package/dist/types-cjs/form/Select.d.ts

@@ -8,9 +8,10 @@ import { SelectBaseProps } from './SelectBase.js';
  * Composes Field, Control, and SelectBase into a single convenience component.
  * Supports all SelectBase props, plus Field-level (label, horizontal) and
  * Control-level (icons) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types-cjs/form/TextArea.d.ts

@@ -8,9 +8,10 @@ import { TextAreaBaseProps } from './TextAreaBase.js';
  * Composes Field, Control, and TextAreaBase into a single convenience component.
  * Supports all TextAreaBase props, plus Field-level (label, horizontal) and
  * Control-level (loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. Inside an outer `Field`, or a `Control` with no
+ * `Field` around it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the

package/dist/types-cjs/form/TimeInput.d.ts

@@ -5,9 +5,12 @@ import { TimeInputBaseProps } from './TimeInputBase.js';
 /**
  * Props for the TimeInput convenience wrapper. Extends `TimeInputBaseProps`
  * with Field-level (label, horizontal) and Control-level (icons, loading) props.
- * Inside an existing `Control` it renders no `Control` of its own, so set the
- * Control-level props on that `Control` instead. Inside an outer `Field`, or a
- * `Control` with no `Field` around it, it renders no `Field` of its own either.
+ * Inside an existing `Control` it renders no `Control` of its own, so its
+ * Control-level props do nothing there and warn in development; set them on
+ * that `Control` instead. In `inline` mode it renders no `Control` anywhere,
+ * so they do nothing inside a `Control` or out, and warn in development
+ * there too. Inside an outer `Field`, or a `Control` with no `Field` around
+ * it, it renders no `Field` of its own either.
  * The exception is `label`, `message`, `horizontal` or `fieldClassName` in that
  * bare `Control`: it keeps a `Field` for them, nested in the `.control`, and
  * warns in development. Wrap the `Control` in a `Field` instead, and set the
@@ -52,7 +55,8 @@ export interface TimeInputProps extends TimeInputBaseProps {
     /**
      * Shows 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; set `isLoading` on that `Control`.
+     * renders none, so this draws nothing and warns in development; set
+     * `isLoading` on that `Control`.
      * Under `prefers-reduced-motion: reduce` the spinner stops and stays
      * drawn (with bestax's CSS loaded).
      */