@allxsmith/bestax-bulma 5.34.0 → 5.34.2

package/dist/types/components/Loading.d.ts

@@ -22,7 +22,11 @@ export interface LoadingProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     size?: 'small' | 'medium' | 'large';
     /** Color variant for the spinner. Default is light grey. */
     color?: LoadingColor;
-    /** Show a cancel button and allow closing. */
+    /**
+     * Show a cancel button and allow closing, by a click on the overlay or by
+     * Escape. An Escape a popup on the page closed on, by calling
+     * `preventDefault()`, doesn't cancel.
+     */
     canCancel?: boolean;
     /** Callback when cancel is triggered. */
     onCancel?: () => void;

package/dist/types/components/Modal.d.ts

@@ -30,7 +30,10 @@ export interface ModalProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     children?: React.ReactNode;
     /**
      * Close the modal when the Escape key is pressed (calls `onClose`). Only the
-     * topmost open modal responds, so Escape closes one layer at a time.
+     * topmost open modal responds, so Escape closes one layer at a time. A popup
+     * inside it, such as a Dropdown's menu or a date picker's calendar, takes
+     * its own Escape first, and so does content that calls `preventDefault()`
+     * on it.
      * @defaultValue true
      */
     closeOnEscape?: boolean;

package/dist/types/components/Sidebar.d.ts

@@ -24,7 +24,11 @@ export interface SidebarProps extends Omit<React.HTMLAttributes<HTMLElement>, 'c
     overlay?: boolean;
     /** Close sidebar when overlay is clicked. Default: true. */
     overlayClose?: boolean;
-    /** Close sidebar on Escape key. Default: true. */
+    /**
+     * Close sidebar on Escape key. A popup inside it, such as a Dropdown's menu
+     * or a date picker's calendar, takes its own Escape first, and so does
+     * content that calls `preventDefault()` on it. Default: true.
+     */
     escapeClose?: boolean;
     /** Allow closing the sidebar. Default: true. */
     canCancel?: boolean;

package/dist/types/components/Toast.d.ts

@@ -34,7 +34,10 @@ export interface ToastProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     rounded?: boolean;
     /** Pause auto-close timer on hover. Default: false. */
     pauseOnHover?: boolean;
-    /** Whether the toast can be dismissed with Escape. Default: true. */
+    /**
+     * Whether the toast can be dismissed with Escape. An Escape a popup on the
+     * page closed on, by calling `preventDefault()`, leaves it up. Default: true.
+     */
     cancelable?: boolean;
     /** Text for an action button (e.g. "Undo"). */
     actionText?: string;

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

@@ -31,7 +31,12 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     data: AutocompleteItem[] | string[];
     /** The current input value (controlled). */
     value?: string;
-    /** The selected item (controlled). */
+    /**
+     * Does nothing: Autocomplete doesn't read it.
+     *
+     * @deprecated Nothing reads it, and `onSelect` is what reports a pick. It
+     * will be removed in the next major version.
+     */
     selected?: AutocompleteItem | string | null;
     /** Placeholder text for the input. */
     placeholder?: string;
@@ -54,7 +59,13 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     selectOnClickOutside?: boolean;
     /** Maximum dropdown height in pixels. */
     maxHeight?: number;
-    /** Render as dropdown style. */
+    /**
+     * Does nothing: Autocomplete doesn't read it, and always shows its
+     * suggestions in a dropdown.
+     *
+     * @deprecated It will be removed in the next major version, with nothing
+     * in its place.
+     */
     dropdown?: boolean;
     /**
      * Show a loading spinner in the input.

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

@@ -12,11 +12,11 @@ export interface FieldProps extends React.HTMLAttributes<HTMLDivElement>, Omit<B
     hasAddons?: boolean | 'centered' | 'right';
     /** Constrains the field to its content's width (used inside horizontal field bodies). */
     narrow?: boolean;
-    /** Field label, rendered above the widget. Automatically names the one control the Field holds: a composed `InputBase`, `SelectBase`, `TextAreaBase`, `DateInputBase`, `TimeInputBase` or `DateTimeInputBase` (an `inline` picker has no input, so it takes nothing), or a bestax input that renders a single input of its own (`Input`, `Select`, `TextArea`, `Numberinput`, `Slider`, `DateInput`, `TimeInput`, `DateTimeInput`, `Autocomplete`, `Taginput`, `File`), adopts a generated id that the label's `htmlFor` points at, and a group (`Radios`, `Checkboxes`, `Rate`, `DateRangeInput`, or a composed `DateRangeInputBase`, `inline` or not) points `aria-labelledby` at the label's own id unless you gave the group an `aria-label` or `aria-labelledby`. A range `Slider` takes the id on its low thumb and also starts each thumb's name with the label through `aria-labelledby`, unless its `ariaLabel` names that thumb or its own `aria-label` or `aria-labelledby` takes the label's place. An `Autocomplete` also names its open suggestion list after the label through `aria-labelledby`. Nothing else takes the label: `Checkbox`, `Radio` and `Switch` are named by their own children, and the label names one only when you wire it as you would any control with an `id` of its own, `labelProps={{ htmlFor }}` plus that control's `id`. Only the single inputs take the `htmlFor`, so once the Field's content has mounted the label keeps it only while one of them holds the id, and drops it over anything else: a group, a `Checkbox`, `Radio` or `Switch`, an `inline` picker, an inner `Field`, an input with an `id` of its own, markup of your own, or nothing at all. A server render, and the first render while hydrating, still write the `htmlFor`, which keeps hydration matching, and an input that mounts later puts it back. The label names an input with an `id` of your own only through `labelProps={{ htmlFor }}` set to that `id`, a `for` it always keeps; `labelProps={{ htmlFor: undefined }}` opts out. Skipped for `grouped`/`hasAddons` fields (multiple controls), and a nested `Field` starts its own scope, so a horizontal Field whose body holds an inner `Field` names the control there only when you wire it. Two controls in one plain labeled Field would both adopt the id, so give each an `id` of its own. */
+    /** Field label, rendered above the widget. Automatically names the one control the Field holds: a composed `InputBase`, `SelectBase`, `TextAreaBase`, `DateInputBase`, `TimeInputBase` or `DateTimeInputBase` (an `inline` picker has no input, so it takes nothing), or a bestax input that renders a single input of its own (`Input`, `Select`, `TextArea`, `Numberinput`, `Slider`, `DateInput`, `TimeInput`, `DateTimeInput`, `Autocomplete`, `Taginput`, `File`), adopts a generated id that the label's `htmlFor` points at, and a group (`Radios`, `Checkboxes`, `Rate`, `DateRangeInput`, or a composed `DateRangeInputBase`, `inline` or not) points `aria-labelledby` at the label's own id unless you gave the group an `aria-label` or `aria-labelledby`. A range `Slider` takes the id on its low thumb and also starts each thumb's name with the label through `aria-labelledby`, unless its `ariaLabel` names that thumb or its own `aria-label` or `aria-labelledby` takes the label's place. An `Autocomplete` or a `Taginput` also names its open suggestion list after the label through `aria-labelledby`. Nothing else takes the label: `Checkbox`, `Radio` and `Switch` are named by their own children, and the label names one only when you wire it as you would any control with an `id` of its own, `labelProps={{ htmlFor }}` plus that control's `id`. Only the single inputs take the `htmlFor`, so once the Field's content has mounted the label keeps it only while one of them holds the id, and drops it over anything else: a group, a `Checkbox`, `Radio` or `Switch`, an `inline` picker, an inner `Field`, an input with an `id` of its own, markup of your own, or nothing at all. A server render, and the first render while hydrating, still write the `htmlFor`, which keeps hydration matching, and an input that mounts later puts it back. The label names an input with an `id` of your own only through `labelProps={{ htmlFor }}` set to that `id`, a `for` it always keeps; `labelProps={{ htmlFor: undefined }}` opts out. Skipped for `grouped`/`hasAddons` fields (multiple controls), and a nested `Field` starts its own scope, so a horizontal Field whose body holds an inner `Field` names the control there only when you wire it. Two controls in one plain labeled Field would both adopt the id, so give each an `id` of its own. */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: 'small' | 'normal' | 'medium' | 'large';
-    /** Props for the label element. An explicit `htmlFor` key — even set to `undefined` — takes over the association. While the association is on, the label renders with the `id` given here, or a generated one, and a group control, a range `Slider`'s thumbs and an `Autocomplete`'s suggestion list point `aria-labelledby` at it. A label you take over gets no generated id, and no group points at it on its own. With an `id` here, though, a range `Slider` or an `Autocomplete` whose `id` your `htmlFor` names still points its thumbs or its suggestion list at it, in a `grouped` or `hasAddons` Field too. To point a group in an inner `Field` at this label by hand, pass that `id`. Nothing in the inner `Field` takes the generated `htmlFor`, so the label drops it after mounting, and adding `htmlFor: undefined` keeps it out of server-rendered markup too. */
+    /** Props for the label element. An explicit `htmlFor` key — even set to `undefined` — takes over the association. While the association is on, the label renders with the `id` given here, or a generated one, and a group control, a range `Slider`'s thumbs and an `Autocomplete`'s or `Taginput`'s suggestion list point `aria-labelledby` at it. A label you take over gets no generated id, and no group points at it on its own. With an `id` here, though, a range `Slider`, an `Autocomplete` or a `Taginput` whose `id` your `htmlFor` names still points its thumbs or its suggestion list at it, in a `grouped` or `hasAddons` Field too. To point a group in an inner `Field` at this label by hand, pass that `id`. Nothing in the inner `Field` takes the generated `htmlFor`, so the label drops it after mounting, and adding `htmlFor: undefined` keeps it out of server-rendered markup too. */
     labelProps?: React.LabelHTMLAttributes<HTMLLabelElement> & {
         [key: string]: unknown;
     };
@@ -71,9 +71,9 @@ export interface FieldBodyProps extends React.HTMLAttributes<HTMLDivElement>, Om
  * `id`, or give the horizontal `Field` a `label` prop, which renders this
  * column and its `<label>` for you. A `<label>` you put here names the
  * control through its `htmlFor` alone: a range `Slider`'s thumbs and an
- * `Autocomplete`'s suggestion list point `aria-labelledby` at a `Field`'s
- * label only when its `label` prop renders it and it names the control.
- * Where it would not name the control on its own, as in an inner `Field`,
+ * `Autocomplete`'s or `Taginput`'s suggestion list point `aria-labelledby` at
+ * a `Field`'s label only when its `label` prop renders it and it names the
+ * control. Where it would not name the control on its own, as in an inner `Field`,
  * pass `labelProps={{ htmlFor, id }}` with a matching `id` on the control.
  *
  * @function

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

@@ -141,7 +141,8 @@ export interface FieldLabelFor {
  * renders with, if it has one. An unlabeled Field passes both through
  * together, so a control in the inner Field of a horizontal layout can tell
  * the outer label names it, and point at that label by its id, as a range
- * Slider's thumbs (#981) and Autocomplete's suggestion list (#998) do. The
+ * Slider's thumbs (#981) and Autocomplete's and Taginput's suggestion lists
+ * (#998, #1082) do. The
  * `htmlFor` is only ever compared with a control's own id, never adopted, so
  * it hands out no id for a control. It keeps the generated id after the
  * label drops a `for` nothing took (#1004), which no control's id matches

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

@@ -26,9 +26,9 @@ type IconLibrary = 'fa' | 'mdi' | 'ion' | 'material-icons' | 'material-symbols';
  * @extraProp {React.Ref<HTMLInputElement>} [ref] - Ref forwarded to the input element.
  */
 export interface TaginputProps extends Omit<React.HTMLAttributes<HTMLDivElement>, 'onChange' | 'defaultValue'>, Omit<BulmaClassesProps, 'color'>, FormFieldProps {
-    /** Field label. Automatically associated with the text input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Not wired when the tag limit is reached (the input is not rendered). Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`) and you set no `id` here; it then replaces the `aria-label="Add tag"` fallback too. */
+    /** Field label. Automatically associated with the text input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Not wired when the tag limit is reached (the input is not rendered). Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`) and you set no `id` here; it then replaces the `aria-label="Add tag"` fallback too. With `data`, the label naming the input also names the open suggestion list, through `aria-labelledby`, when it has an id: this label always does, and an outer `Field`'s does unless you wired it by hand without an `id` in its `labelProps`. Otherwise the list is named "Suggestions". */
     label?: React.ReactNode;
-    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). */
+    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). With `data`, while the label names the input, the suggestion list's `aria-labelledby` points at it, through an `id` here when you give one and a generated one otherwise. */
     labelProps?: React.LabelHTMLAttributes<HTMLLabelElement> & {
         [key: string]: unknown;
     };
@@ -38,7 +38,12 @@ export interface TaginputProps extends Omit<React.HTMLAttributes<HTMLDivElement>
     value?: TaginputTag[];
     /** Default tags (uncontrolled). */
     defaultValue?: TaginputTag[];
-    /** Autocomplete suggestions. */
+    /**
+     * Autocomplete suggestions. With `data` set, even to an empty array, the
+     * text input is a `role="combobox"` that controls the suggestion list and
+     * points `aria-activedescendant` at the highlighted suggestion. Without it
+     * there's no list, so the input stays a plain text field.
+     */
     data?: string[];
     /** Placeholder text when no tags. */
     placeholder?: string;

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

@@ -20,8 +20,8 @@ interface UseAutoLabelIdOptions {
     hasInput?: boolean;
     /**
      * True when the control also points `aria-labelledby` at the label, as a
-     * range Slider's thumbs (#981) and Autocomplete's suggestion list (#998)
-     * do, so it needs the label's own id. Its own label then gets one
+     * range Slider's thumbs (#981) and Autocomplete's and Taginput's
+     * suggestion lists (#998, #1082) do, so it needs the label's own id. Its own label then gets one
      * (`labelProps.id` when given, otherwise a generated one), and the hook
      * returns it, or a surrounding Field's, as `labelId`.
      */

package/dist/types-cjs/components/Loading.d.ts

@@ -22,7 +22,11 @@ export interface LoadingProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     size?: 'small' | 'medium' | 'large';
     /** Color variant for the spinner. Default is light grey. */
     color?: LoadingColor;
-    /** Show a cancel button and allow closing. */
+    /**
+     * Show a cancel button and allow closing, by a click on the overlay or by
+     * Escape. An Escape a popup on the page closed on, by calling
+     * `preventDefault()`, doesn't cancel.
+     */
     canCancel?: boolean;
     /** Callback when cancel is triggered. */
     onCancel?: () => void;

package/dist/types-cjs/components/Modal.d.ts

@@ -30,7 +30,10 @@ export interface ModalProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     children?: React.ReactNode;
     /**
      * Close the modal when the Escape key is pressed (calls `onClose`). Only the
-     * topmost open modal responds, so Escape closes one layer at a time.
+     * topmost open modal responds, so Escape closes one layer at a time. A popup
+     * inside it, such as a Dropdown's menu or a date picker's calendar, takes
+     * its own Escape first, and so does content that calls `preventDefault()`
+     * on it.
      * @defaultValue true
      */
     closeOnEscape?: boolean;

package/dist/types-cjs/components/Sidebar.d.ts

@@ -24,7 +24,11 @@ export interface SidebarProps extends Omit<React.HTMLAttributes<HTMLElement>, 'c
     overlay?: boolean;
     /** Close sidebar when overlay is clicked. Default: true. */
     overlayClose?: boolean;
-    /** Close sidebar on Escape key. Default: true. */
+    /**
+     * Close sidebar on Escape key. A popup inside it, such as a Dropdown's menu
+     * or a date picker's calendar, takes its own Escape first, and so does
+     * content that calls `preventDefault()` on it. Default: true.
+     */
     escapeClose?: boolean;
     /** Allow closing the sidebar. Default: true. */
     canCancel?: boolean;

package/dist/types-cjs/components/Toast.d.ts

@@ -34,7 +34,10 @@ export interface ToastProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     rounded?: boolean;
     /** Pause auto-close timer on hover. Default: false. */
     pauseOnHover?: boolean;
-    /** Whether the toast can be dismissed with Escape. Default: true. */
+    /**
+     * Whether the toast can be dismissed with Escape. An Escape a popup on the
+     * page closed on, by calling `preventDefault()`, leaves it up. Default: true.
+     */
     cancelable?: boolean;
     /** Text for an action button (e.g. "Undo"). */
     actionText?: string;

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

@@ -31,7 +31,12 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     data: AutocompleteItem[] | string[];
     /** The current input value (controlled). */
     value?: string;
-    /** The selected item (controlled). */
+    /**
+     * Does nothing: Autocomplete doesn't read it.
+     *
+     * @deprecated Nothing reads it, and `onSelect` is what reports a pick. It
+     * will be removed in the next major version.
+     */
     selected?: AutocompleteItem | string | null;
     /** Placeholder text for the input. */
     placeholder?: string;
@@ -54,7 +59,13 @@ export interface AutocompleteProps extends Omit<React.HTMLAttributes<HTMLDivElem
     selectOnClickOutside?: boolean;
     /** Maximum dropdown height in pixels. */
     maxHeight?: number;
-    /** Render as dropdown style. */
+    /**
+     * Does nothing: Autocomplete doesn't read it, and always shows its
+     * suggestions in a dropdown.
+     *
+     * @deprecated It will be removed in the next major version, with nothing
+     * in its place.
+     */
     dropdown?: boolean;
     /**
      * Show a loading spinner in the input.

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

@@ -12,11 +12,11 @@ export interface FieldProps extends React.HTMLAttributes<HTMLDivElement>, Omit<B
     hasAddons?: boolean | 'centered' | 'right';
     /** Constrains the field to its content's width (used inside horizontal field bodies). */
     narrow?: boolean;
-    /** Field label, rendered above the widget. Automatically names the one control the Field holds: a composed `InputBase`, `SelectBase`, `TextAreaBase`, `DateInputBase`, `TimeInputBase` or `DateTimeInputBase` (an `inline` picker has no input, so it takes nothing), or a bestax input that renders a single input of its own (`Input`, `Select`, `TextArea`, `Numberinput`, `Slider`, `DateInput`, `TimeInput`, `DateTimeInput`, `Autocomplete`, `Taginput`, `File`), adopts a generated id that the label's `htmlFor` points at, and a group (`Radios`, `Checkboxes`, `Rate`, `DateRangeInput`, or a composed `DateRangeInputBase`, `inline` or not) points `aria-labelledby` at the label's own id unless you gave the group an `aria-label` or `aria-labelledby`. A range `Slider` takes the id on its low thumb and also starts each thumb's name with the label through `aria-labelledby`, unless its `ariaLabel` names that thumb or its own `aria-label` or `aria-labelledby` takes the label's place. An `Autocomplete` also names its open suggestion list after the label through `aria-labelledby`. Nothing else takes the label: `Checkbox`, `Radio` and `Switch` are named by their own children, and the label names one only when you wire it as you would any control with an `id` of its own, `labelProps={{ htmlFor }}` plus that control's `id`. Only the single inputs take the `htmlFor`, so once the Field's content has mounted the label keeps it only while one of them holds the id, and drops it over anything else: a group, a `Checkbox`, `Radio` or `Switch`, an `inline` picker, an inner `Field`, an input with an `id` of its own, markup of your own, or nothing at all. A server render, and the first render while hydrating, still write the `htmlFor`, which keeps hydration matching, and an input that mounts later puts it back. The label names an input with an `id` of your own only through `labelProps={{ htmlFor }}` set to that `id`, a `for` it always keeps; `labelProps={{ htmlFor: undefined }}` opts out. Skipped for `grouped`/`hasAddons` fields (multiple controls), and a nested `Field` starts its own scope, so a horizontal Field whose body holds an inner `Field` names the control there only when you wire it. Two controls in one plain labeled Field would both adopt the id, so give each an `id` of its own. */
+    /** Field label, rendered above the widget. Automatically names the one control the Field holds: a composed `InputBase`, `SelectBase`, `TextAreaBase`, `DateInputBase`, `TimeInputBase` or `DateTimeInputBase` (an `inline` picker has no input, so it takes nothing), or a bestax input that renders a single input of its own (`Input`, `Select`, `TextArea`, `Numberinput`, `Slider`, `DateInput`, `TimeInput`, `DateTimeInput`, `Autocomplete`, `Taginput`, `File`), adopts a generated id that the label's `htmlFor` points at, and a group (`Radios`, `Checkboxes`, `Rate`, `DateRangeInput`, or a composed `DateRangeInputBase`, `inline` or not) points `aria-labelledby` at the label's own id unless you gave the group an `aria-label` or `aria-labelledby`. A range `Slider` takes the id on its low thumb and also starts each thumb's name with the label through `aria-labelledby`, unless its `ariaLabel` names that thumb or its own `aria-label` or `aria-labelledby` takes the label's place. An `Autocomplete` or a `Taginput` also names its open suggestion list after the label through `aria-labelledby`. Nothing else takes the label: `Checkbox`, `Radio` and `Switch` are named by their own children, and the label names one only when you wire it as you would any control with an `id` of its own, `labelProps={{ htmlFor }}` plus that control's `id`. Only the single inputs take the `htmlFor`, so once the Field's content has mounted the label keeps it only while one of them holds the id, and drops it over anything else: a group, a `Checkbox`, `Radio` or `Switch`, an `inline` picker, an inner `Field`, an input with an `id` of its own, markup of your own, or nothing at all. A server render, and the first render while hydrating, still write the `htmlFor`, which keeps hydration matching, and an input that mounts later puts it back. The label names an input with an `id` of your own only through `labelProps={{ htmlFor }}` set to that `id`, a `for` it always keeps; `labelProps={{ htmlFor: undefined }}` opts out. Skipped for `grouped`/`hasAddons` fields (multiple controls), and a nested `Field` starts its own scope, so a horizontal Field whose body holds an inner `Field` names the control there only when you wire it. Two controls in one plain labeled Field would both adopt the id, so give each an `id` of its own. */
     label?: React.ReactNode;
     /** Size for the label. */
     labelSize?: 'small' | 'normal' | 'medium' | 'large';
-    /** Props for the label element. An explicit `htmlFor` key — even set to `undefined` — takes over the association. While the association is on, the label renders with the `id` given here, or a generated one, and a group control, a range `Slider`'s thumbs and an `Autocomplete`'s suggestion list point `aria-labelledby` at it. A label you take over gets no generated id, and no group points at it on its own. With an `id` here, though, a range `Slider` or an `Autocomplete` whose `id` your `htmlFor` names still points its thumbs or its suggestion list at it, in a `grouped` or `hasAddons` Field too. To point a group in an inner `Field` at this label by hand, pass that `id`. Nothing in the inner `Field` takes the generated `htmlFor`, so the label drops it after mounting, and adding `htmlFor: undefined` keeps it out of server-rendered markup too. */
+    /** Props for the label element. An explicit `htmlFor` key — even set to `undefined` — takes over the association. While the association is on, the label renders with the `id` given here, or a generated one, and a group control, a range `Slider`'s thumbs and an `Autocomplete`'s or `Taginput`'s suggestion list point `aria-labelledby` at it. A label you take over gets no generated id, and no group points at it on its own. With an `id` here, though, a range `Slider`, an `Autocomplete` or a `Taginput` whose `id` your `htmlFor` names still points its thumbs or its suggestion list at it, in a `grouped` or `hasAddons` Field too. To point a group in an inner `Field` at this label by hand, pass that `id`. Nothing in the inner `Field` takes the generated `htmlFor`, so the label drops it after mounting, and adding `htmlFor: undefined` keeps it out of server-rendered markup too. */
     labelProps?: React.LabelHTMLAttributes<HTMLLabelElement> & {
         [key: string]: unknown;
     };
@@ -71,9 +71,9 @@ export interface FieldBodyProps extends React.HTMLAttributes<HTMLDivElement>, Om
  * `id`, or give the horizontal `Field` a `label` prop, which renders this
  * column and its `<label>` for you. A `<label>` you put here names the
  * control through its `htmlFor` alone: a range `Slider`'s thumbs and an
- * `Autocomplete`'s suggestion list point `aria-labelledby` at a `Field`'s
- * label only when its `label` prop renders it and it names the control.
- * Where it would not name the control on its own, as in an inner `Field`,
+ * `Autocomplete`'s or `Taginput`'s suggestion list point `aria-labelledby` at
+ * a `Field`'s label only when its `label` prop renders it and it names the
+ * control. Where it would not name the control on its own, as in an inner `Field`,
  * pass `labelProps={{ htmlFor, id }}` with a matching `id` on the control.
  *
  * @function

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

@@ -141,7 +141,8 @@ export interface FieldLabelFor {
  * renders with, if it has one. An unlabeled Field passes both through
  * together, so a control in the inner Field of a horizontal layout can tell
  * the outer label names it, and point at that label by its id, as a range
- * Slider's thumbs (#981) and Autocomplete's suggestion list (#998) do. The
+ * Slider's thumbs (#981) and Autocomplete's and Taginput's suggestion lists
+ * (#998, #1082) do. The
  * `htmlFor` is only ever compared with a control's own id, never adopted, so
  * it hands out no id for a control. It keeps the generated id after the
  * label drops a `for` nothing took (#1004), which no control's id matches

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

@@ -26,9 +26,9 @@ type IconLibrary = 'fa' | 'mdi' | 'ion' | 'material-icons' | 'material-symbols';
  * @extraProp {React.Ref<HTMLInputElement>} [ref] - Ref forwarded to the input element.
  */
 export interface TaginputProps extends Omit<React.HTMLAttributes<HTMLDivElement>, 'onChange' | 'defaultValue'>, Omit<BulmaClassesProps, 'color'>, FormFieldProps {
-    /** Field label. Automatically associated with the text input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Not wired when the tag limit is reached (the input is not rendered). Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`) and you set no `id` here; it then replaces the `aria-label="Add tag"` fallback too. */
+    /** Field label. Automatically associated with the text input via `htmlFor` — uses your `id` when provided, otherwise a generated one. Not wired when the tag limit is reached (the input is not rendered). Dropped inside an outer `Field`, whose own label associates instead when that `Field` generates a target id (not `grouped`/`hasAddons`, no explicit `labelProps.htmlFor`) and you set no `id` here; it then replaces the `aria-label="Add tag"` fallback too. With `data`, the label naming the input also names the open suggestion list, through `aria-labelledby`, when it has an id: this label always does, and an outer `Field`'s does unless you wired it by hand without an `id` in its `labelProps`. Otherwise the list is named "Suggestions". */
     label?: React.ReactNode;
-    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). */
+    /** Props for the label element. An explicit `htmlFor` here overrides the automatic association (no id is generated then). With `data`, while the label names the input, the suggestion list's `aria-labelledby` points at it, through an `id` here when you give one and a generated one otherwise. */
     labelProps?: React.LabelHTMLAttributes<HTMLLabelElement> & {
         [key: string]: unknown;
     };
@@ -38,7 +38,12 @@ export interface TaginputProps extends Omit<React.HTMLAttributes<HTMLDivElement>
     value?: TaginputTag[];
     /** Default tags (uncontrolled). */
     defaultValue?: TaginputTag[];
-    /** Autocomplete suggestions. */
+    /**
+     * Autocomplete suggestions. With `data` set, even to an empty array, the
+     * text input is a `role="combobox"` that controls the suggestion list and
+     * points `aria-activedescendant` at the highlighted suggestion. Without it
+     * there's no list, so the input stays a plain text field.
+     */
     data?: string[];
     /** Placeholder text when no tags. */
     placeholder?: string;

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

@@ -20,8 +20,8 @@ interface UseAutoLabelIdOptions {
     hasInput?: boolean;
     /**
      * True when the control also points `aria-labelledby` at the label, as a
-     * range Slider's thumbs (#981) and Autocomplete's suggestion list (#998)
-     * do, so it needs the label's own id. Its own label then gets one
+     * range Slider's thumbs (#981) and Autocomplete's and Taginput's
+     * suggestion lists (#998, #1082) do, so it needs the label's own id. Its own label then gets one
      * (`labelProps.id` when given, otherwise a generated one), and the hook
      * returns it, or a surrounding Field's, as `labelId`.
      */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allxsmith/bestax-bulma",
-  "version": "5.34.0",
+  "version": "5.34.2",
   "description": "A fully-typed React component library for the Bulma CSS framework. Build modern UIs quickly with reusable, accessible, and customizable Bulma-based React components.",
   "main": "dist/index.cjs",
   "module": "dist/index.esm.js",