@cube-dev/ui-kit 0.194.1 → 0.196.0

package/docs/components/fields/TextArea.md

@@ -37,7 +37,7 @@ These properties allow direct style application without using the `styles` prop:
 - **`autoSize`** `boolean` (default: `false`) — Whether the textarea should automatically resize based on content
 - **`maxRows`** `number` (default: `10`) — Maximum number of visible rows when `autoSize` is enabled
 - **`rows`** `number` (default: `3`) — Number of visible text rows
-- **`value`** `string` — The text value in controlled mode
+- **`value`** `string | null` — The text value in controlled mode. `null` clears the field and keeps it controlled
 - **`defaultValue`** `string` — The default text value in uncontrolled mode
 - **`isBuffered`** `boolean` (default: `true`) — Whether typed text is held locally until the controlled `value` catches up. This is what keeps the caret in place when the value round-trips through a store that re-renders a pass late; `onChange` still fires on every keystroke. Set to `false` for a caller that must see the field snap back to its own `value` the moment it declines a keystroke.
 - **`placeholder`** `string` — Placeholder text when input is empty
@@ -50,11 +50,12 @@ These properties allow direct style application without using the `styles` prop:
 - **`autoComplete`** `string` — HTML [`autocomplete`](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete) token that tells the browser what to autofill (`street-address`, `off`, …). The lowercase `autocomplete` alias is deprecated.
 - **`maxLength`** `number` — Maximum number of characters allowed
 - **`minLength`** `number` — Minimum number of characters required
-- **`inputProps`** `Props` — Direct HTML props passed to the inner textarea element, merged over the props React Aria generates: a key you set wins, and event handlers are chained rather than replaced
+- **`inputProps`** `Props` — Direct HTML props passed to the inner textarea element, merged over the props React Aria generates: a key you set wins, and event handlers are chained rather than replaced. The explicit `isDisabled`, `maxLength`, `minLength`, `autoFocus` and `autoComplete` props win over the same attributes in `inputProps` when they are set; one left unset keeps the `inputProps` value. Set the row count with `rows`, which always applies
 - **`wrapperProps`** `Props` — Additional HTML props passed to the input wrapper container
 - **`inputRef`** `RefObject<HTMLTextAreaElement>` — Ref to the inner textarea element
 - **`wrapperRef`** `RefObject<HTMLDivElement>` — Ref to the input wrapper container
-- **`loadingIndicator`** `ReactNode` — Custom loading indicator element
+- **`loadingIndicator`** `ReactNode` — Rendered in place of the default loading icon while `isLoading` is set
+- **`validate`** `(value: string) => ValidationError | true | null | undefined` — Client-side validation. React Aria sets `aria-invalid` from the returned errors at once; the invalid style and the message follow after the user edits or leaves the field, so an empty field does not open in red. An explicit `errorMessage` replaces the returned message, and an explicit `isInvalid` (or a form's validation) takes over from `validate` entirely
 - **`inputStyles`** `Styles` — Custom styles for the textarea element
 - **`onChange`** `function` — Callback fired when the input value changes
 - **`onBlur`** `function` — Callback fired when the input loses focus

package/docs/components/fields/TextInput.md

@@ -16,7 +16,7 @@ A text input component that allows users to input custom text entries with a key
 
 ### Properties
 
-- **`value`** `string` — The text value in controlled mode
+- **`value`** `string | null` — The text value in controlled mode. `null` clears the field and keeps it controlled
 - **`defaultValue`** `string` — The default text value in uncontrolled mode
 - **`isBuffered`** `boolean` (default: `true`) — Whether typed text is held locally until the controlled `value` catches up. This is what keeps the caret in place when the value round-trips through a store that re-renders a pass late; `onChange` still fires on every keystroke. Set to `false` for a caller that must see the field snap back to its own `value` the moment it declines a keystroke.
 - **`placeholder`** `string` — Placeholder text when input is empty
@@ -32,10 +32,11 @@ A text input component that allows users to input custom text entries with a key
 - **`autoComplete`** `string` — HTML [`autocomplete`](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete) token that tells the browser what to autofill (`email`, `username`, `off`, …). The lowercase `autocomplete` alias is deprecated.
 - **`maxLength`** `number` — Maximum number of characters allowed
 - **`minLength`** `number` — Minimum number of characters required
-- **`inputProps`** `Props` — Direct HTML props passed to the inner input element, merged over the props React Aria generates: a key you set wins, and event handlers are chained rather than replaced
+- **`inputProps`** `Props` — Direct HTML props passed to the inner input element, merged over the props React Aria generates: a key you set wins, and event handlers are chained rather than replaced. The explicit `isDisabled`, `maxLength`, `minLength`, `autoFocus`, `rows` and `autoComplete` props win over the same attributes in `inputProps` when they are set; one left unset keeps the `inputProps` value
 - **`inputRef`** `RefObject<HTMLInputElement | HTMLTextAreaElement>` — Ref to the inner input element
 - **`wrapperRef`** `RefObject<HTMLDivElement>` — Ref to the input wrapper container
-- **`loadingIndicator`** `ReactNode` — Custom loading indicator element
+- **`loadingIndicator`** `ReactNode` — Rendered in place of the default loading icon while `isLoading` is set
+- **`validate`** `(value: string) => ValidationError | true | null | undefined` — Client-side validation. React Aria sets `aria-invalid` from the returned errors at once; the invalid style and the message follow after the user edits or leaves the field, so an empty field does not open in red. An explicit `errorMessage` replaces the returned message, and an explicit `isInvalid` (or a form's validation) takes over from `validate` entirely
 - **`onChange`** `function` — Callback fired when the input value changes
 - **`onBlur`** `function` — Callback fired when the input loses focus
 - **`onFocus`** `function` — Callback fired when the input receives focus
@@ -110,10 +111,12 @@ These properties allow direct style application without using the `styles` prop:
 The `mods` prop accepts the following modifiers you can override:
 
 - **`focused`** `boolean` — Forces focus ring appearance.
+- **`hovered`** `boolean` — Forces hover appearance.
 - **`disabled`** `boolean` — Forces disabled appearance.
 - **`invalid`** `boolean` — Forces invalid state styling.
 - **`valid`** `boolean` — Forces valid state styling.
-- **`loading`** `boolean` — Displays loading spinner.
+- **`loadable`** `boolean` — Set when a `loadingIndicator` is given. The loading icon itself follows `isLoading`, which has no modifier.
+- **`multiline`** `boolean` — Set for a multiline input.
 - **`prefix`** `boolean` — Indicates presence of prefix content.
 - **`suffix`** `boolean` — Indicates presence of suffix content.
 
@@ -189,18 +192,22 @@ import { IconMail } from '@tabler/icons-react';
 - `Shift + Tab` – Moves focus away from the input
 - Standard text editing shortcuts (Ctrl+A, Ctrl+C, etc.)
 
+### Pointer
+
+A press anywhere inside the field's border focuses the input, including the prefix and suffix areas and their icons. Presses on interactive content there, such as a button in `suffix`, stay with that content.
+
 ### Screen Reader Support
 
 - Announces role "textbox" or "searchbox" for search inputs
 - Announces label, description, and validation messages
 - State changes like "invalid" or "required" are announced
-- Loading state is announced to screen readers
+- The loading indicator is visual only: `isLoading` is not announced, so announce a long-running check yourself if users need to hear it
 
 ### ARIA Properties
 
 - `aria-label`, `aria-labelledby` – Accessible name for the input
 - `aria-describedby` – Links to description and error messages
-- `aria-invalid` – Managed automatically based on `isInvalid`
+- `aria-invalid` – Managed automatically based on `isInvalid` and `validate`
 - `aria-required` – Set when `isRequired` is true
 - Additional ARIA attributes supported by React Aria's `useTextField`
 

package/docs/components/overlays/AlertDialog.md

@@ -12,7 +12,7 @@ A modal dialog for important messages that require user acknowledgment. Extends
 
 - **`title`** `string` — Dialog title
 - **`content`** `ReactNode` — Dialog body content
-- **`danger`** `boolean` — Applies danger styling for destructive actions
+- **`danger`** `boolean` — Marks the confirm action as destructive. It gets danger styling, and the dialog opens with focus on Cancel, or on the dialog itself when there is no Cancel, so a reflexive Enter does not run it. An explicit `autoFocus` on `actions.confirm` still puts focus there. Without `danger`, the confirm button takes focus
 - **`noActions`** `boolean` — Hide the action buttons entirely
 - **`actions`** `object` — Customize buttons:
   - `confirm` — Confirm button props or `false` to hide (default: `{ children: 'Ok', type: 'primary' }`)
@@ -66,9 +66,15 @@ These properties allow direct style application without using the `styles` prop:
 />
 ```
 
+## Accessibility
+
+- The dialog has `role="alertdialog"`. Its title is its name, and its `content` is its description (`aria-describedby`), so a screen reader reads the message when the dialog opens
+- Focus starts on the confirm button, or on Cancel (the dialog itself without one) when `danger` is set and the confirm action does not set `autoFocus`
+- Focus stays inside the dialog until it closes, then returns to the element that opened it
+
 ## Imperative API
 
-`useAlertDialogAPI()` opens an alert dialog from code, such as an event handler, with no `DialogTrigger` to render. It works anywhere under `<Root>`.
+`useAlertDialogAPI()` opens an alert dialog from code, such as an event handler, with no `DialogTrigger` to render. It works anywhere under `<Root>`. A dialog belongs to the component that calls the hook and closes when that component unmounts; see [The dialog's owner](#the-dialogs-owner).
 
 - **`open(props, params?)`** `Promise<'confirm' | 'secondary'>` — Opens the dialog. Resolves with the action the user picked, and rejects when the dialog closes without one or cannot open.
 
@@ -76,7 +82,7 @@ These properties allow direct style application without using the `styles` prop:
 
 - **`onConfirm`** `() => unknown` — Runs when the confirm button is pressed. If it returns a promise, the dialog stays open until it settles (see below)
 - **`onSecondary`** `() => unknown` — The same, for the secondary button
-- **`onCancel`** `() => void` — Runs when the dialog settles as a cancel: the Cancel button, Escape, a click outside, an aborted `cancelToken`, or `content` calling `reject()`
+- **`onCancel`** `() => void` — Runs when the dialog settles as a cancel: the Cancel button, Escape, a click outside, an aborted `cancelToken`, the unmount of the component that opened it, or `content` calling `reject()`
 - **`type`** — The dialog container type, as on `DialogContainer`
 - **`isDismissable`** `boolean` (default: `true`) — Whether Escape and a click outside close the dialog
 - **`onDismiss`** `(action?: string) => void` — Called when an action button, Escape or a click outside closes the dialog. An action button passes its name: `'confirm'`, `'secondary'` or `'cancel'`
@@ -84,7 +90,7 @@ These properties allow direct style application without using the `styles` prop:
 
 `params` takes:
 
-- **`cancelToken`** `AbortSignal` — Closes the dialog when aborted
+- **`cancelToken`** `AbortSignal` — Closes the dialog when aborted. A running confirm or secondary action finishes first
 
 The confirm button resolves `'confirm'` whether you configure `actions.confirm` or leave the default Ok button. Set it to `false` to hide it.
 
@@ -142,6 +148,7 @@ open({
 | Cancel action | rejects with `undefined` |
 | Escape or a click outside | rejects with `undefined` |
 | `cancelToken` aborted, before or while the dialog is open | rejects with `undefined` |
+| The component that opened it unmounts | rejects with `undefined` |
 | `content` calls `resolve(status)` | resolves `status` |
 | `content` calls `reject(reason)` | rejects with `reason` (`undefined` for `reject()`) |
 | Another alert dialog is open | rejects with an `Error` |
@@ -190,7 +197,40 @@ const onRequestApproval = () => {
 controllerRef.current?.abort();
 ```
 
-Aborting settles the dialog as a cancel. A signal that is already aborted settles it right away, without showing the dialog.
+Aborting settles the dialog as a cancel. A signal that is already aborted settles it right away, without showing the dialog. If the confirm or secondary action is running, it finishes first: the dialog closes with its result, or as a cancel if it fails.
+
+### The dialog's owner
+
+A dialog belongs to the component that called `useAlertDialogAPI()`. When that component unmounts, the dialog closes as a cancel, as if its own `cancelToken` were aborted. Its callbacks are that component's code, and a dialog left open would run them against a component that is gone. A call to `open` after the unmount, such as one after an `await`, settles as a cancel without opening. A running confirm or secondary action finishes first, so a list row whose delete removes it still resolves `'confirm'`.
+
+So call the hook in a component that stays mounted while the dialog is open. A menu closes when its item is pressed, so call the hook in the component that renders the menu and pass `open` down, rather than calling it in the item:
+
+```jsx
+function RowActions({ row }) {
+  // Stays mounted after the menu closes.
+  const { open } = useAlertDialogAPI();
+
+  return (
+    <MenuTrigger>
+      <Button>Actions</Button>
+      <Menu
+        onAction={(key) => {
+          if (key === 'delete') {
+            open({
+              title: `Delete ${row.name}?`,
+              danger: true,
+              actions: { confirm: { children: 'Delete' }, cancel: true },
+              onConfirm: () => deleteRow(row.id),
+            });
+          }
+        }}
+      >
+        <Menu.Item key="delete">Delete</Menu.Item>
+      </Menu>
+    </MenuTrigger>
+  );
+}
+```
 
 ### One dialog at a time
 

package/docs/components/overlays/Dialog.md

@@ -183,16 +183,16 @@ The body is the `Content` that is a direct child of the dialog or of a direct-ch
 
 ### Screen Reader Support
 
-- Dialog announces as "dialog" or "alertdialog" based on role
-- Focus is trapped within the dialog when open
+- Dialog announces as "dialog" or "alertdialog" based on role, with its title as its name
+- An alert dialog also reads its `Content`, the message, as its description. A plain dialog reads only its title on open, so a form inside it is not read field by field; link a short description with `aria-describedby` when the title alone is not enough
+- Focus moves into the dialog when it opens: to an input marked `data-autofocus`, or to a submit or primary button, otherwise to the dialog itself. In an alert dialog this never picks a destructive (`danger`) button
+- Focus is contained within the dialog from the moment it opens, including while it animates in. A `panel` dialog does not contain focus, nor does a popover opened by a `DialogTrigger` with `isDismissable={false}`
 - Focus returns to the trigger element when dialog closes
-- Dialog title and content are properly announced
-- State changes and actions are communicated to screen readers
 
 ### ARIA Properties
 
 - `aria-labelledby` - Links dialog to its title element automatically
-- `aria-describedby` - Links dialog to its description content
+- `aria-describedby` - Set automatically only for `role="alertdialog"`, where it links the dialog to its `Content`. A plain dialog links nothing unless you pass `aria-describedby` with the id of the element that describes it. An explicit `aria-describedby` always wins
 - `aria-modal` - Not set. While a modal, fullscreen or tray dialog is open, the page behind it is `aria-hidden` instead, so a screen reader's reading cursor stays in the dialog. Lists, menus and popovers opened from the dialog render outside it and stay readable, which `aria-modal` would prevent. Popover and panel dialogs leave the page readable
 - `role` - Set to "dialog" or "alertdialog" based on content type
 

package/docs/components/overlays/DialogTrigger.md

@@ -19,13 +19,13 @@ DialogTrigger serves as a wrapper around a Dialog and its associated trigger, li
 - **`type`** `'modal' | 'popover' | 'tray' | 'fullscreen' | 'fullscreenTakeover' | 'panel'` (default: `modal`) — The type of Dialog that should be rendered
 - **`mobileType`** `'modal' | 'tray' | 'fullscreen' | 'fullscreenTakeover' | 'panel' | 'popover'` (default: same as `type`) — The Dialog type on mobile
 - **`placement`** `'top' | 'bottom' | 'left' | 'right' | 'top start' | 'top end' | 'bottom start' | 'bottom end' | 'left top' | 'left bottom' | 'right top' | 'right bottom'` — The placement of the dialog relative to its trigger
-- **`hideArrow`** `boolean` (default: `false`) — Whether a popover type Dialog's arrow should be hidden
+- **`hideArrow`** `boolean` — **Deprecated.** Has no effect: popovers render no arrow, so there is nothing to hide
 - **`mobileViewport`** `number` (default: `700`) — The screen breakpoint for the mobile type
-- **`isDismissable`** `boolean` (default: `true`) — Whether passive dismissal (Escape or an outside click) can close the dialog. Explicit dialog actions, such as Submit and Cancel, can still close it.
+- **`isDismissable`** `boolean` (default: `true`) — Whether passive dismissal (Escape or an outside click) can close the dialog. Explicit dialog actions, such as Submit and Cancel, can still close it. A popover that is not dismissable leaves outside presses alone: the control pressed still receives the press, and a text field there can take focus, because such a popover does not hold focus. It stays open when another popover opens, and closes when a modal, tray, fullscreen or panel dialog opens from another `DialogTrigger`.
 - **`isKeyboardDismissDisabled`** `boolean` (default: `false`) — Whether pressing the escape key to close the dialog should be disabled
 - **`isOpen`** `boolean` — Whether the dialog is open (controlled)
 - **`defaultOpen`** `boolean` (default: `false`) — Whether the dialog is open by default (uncontrolled)
-- **`offset`** `number` (default: `8`) — The additional offset applied along the main axis
+- **`offset`** `number` (default: `8`) — The gap between the trigger and a popover, along the main axis. `0` places the popover flush against the trigger
 - **`crossOffset`** `number` (default: `0`) — The additional offset applied along the cross axis
 - **`containerPadding`** `number` (default: `12`) — The padding between the edge of the overlay and the boundary
 - **`shouldFlip`** `boolean` (default: `true`) — Whether the overlay should flip positions when insufficient space
@@ -33,7 +33,7 @@ DialogTrigger serves as a wrapper around a Dialog and its associated trigger, li
 - **`hideOnClose`** `boolean` — Whether to hide the overlay instead of unmounting on close
 - **`onOpenChange`** `function` — Callback fired when the dialog open state changes
 - **`onDismiss`** `function` — Callback fired when the dialog is dismissed
-- **`targetRef`** — The ref of the element the Dialog should visually attach itself to
+- **`targetRef`** — The ref of the element the Dialog should visually attach itself to. A popover closes when this element scrolls, as one attached to its trigger does
 - **`styles`** — The style map for the overlay
 - **`shouldCloseOnInteractOutside`** `(element: Element) => boolean` — Function to determine if a popover type Dialog should close on outside interaction. Asked before every built-in dismiss behaviour, so returning `false` keeps the popover open even for a `Button` / `ItemButton` that would otherwise dismiss it, or for a control the trigger itself owns (a picker's clear button, its custom `actions`) that would otherwise be read as a press on the trigger — and the pressed control still receives its own click. The element passed is the deepest node under the pointer (for a `Button` that is the label inside it, not the `<button>`), so guard with `contains()` rather than an identity check
 - **`shouldRestoreFocus`** `boolean` (default: `true`) — Whether focus returns to the trigger when the dialog closes. Only needed for a surface that claims focus _later_ than the restore (async load, entry animation); an action that focuses the surface it opens is already left alone — see [Focus Management](#best-practices)
@@ -158,7 +158,7 @@ function ControlledDialog() {
 ### Screen Reader Support
 
 - Dialog announces as "dialog" to screen readers
-- Focus is trapped within the dialog when open
+- Focus is contained within the dialog from the moment it opens, including while it animates in. A popover with `isDismissable={false}` does not contain focus, so focus can follow a press outside it
 - Focus returns to trigger element when dialog closes
 - The page behind a modal, fullscreen or tray dialog is hidden from screen readers while it is open; lists, menus and popovers opened from the dialog stay readable. Popover and panel dialogs leave the page readable
 - Proper ARIA attributes are applied automatically
@@ -168,7 +168,7 @@ function ControlledDialog() {
 - `aria-haspopup` - Automatically applied to trigger element
 - `aria-expanded` - Indicates dialog open state
 - `aria-labelledby` - Links dialog to its title
-- `aria-describedby` - Links dialog to its description
+- `aria-describedby` - Set for an alert dialog, linking its message; see [Dialog](./Dialog.md#aria-properties)
 
 ## Best Practices
 

package/docs/components/overlays/Tooltip.md

@@ -39,14 +39,14 @@ Display container for tooltip content. Has a directional arrow dependent on its
 ### Properties
 
 - **`tipStyles`** `Styles` — Custom styles for the tooltip arrow (tip) element
-- **`showIcon`** `boolean` — Controls whether an icon should be displayed in the tooltip
+- **`showIcon`** `boolean` — Deprecated. Has no effect
 - **`placement`** `PlacementAxis` (default: `'top'`) — Position of the tooltip relative to its trigger. Options: `top`, `bottom`, `left`, `right`
 - **`isMaterial`** `boolean` — Enables material-style tooltip with auto pointer events
 - **`isLight`** `boolean` — Uses light color scheme for the tooltip
 - **`isOpen`** `boolean` — Controlled open state of the tooltip
 - **`defaultOpen`** `boolean` — Whether the tooltip is open by default (uncontrolled)
 - **`onOpenChange`** `(isOpen: boolean) => void` — Callback when the tooltip open state changes
-- **`shouldFlip`** `boolean` — Whether the tooltip should flip position when there is insufficient space
+- **`shouldFlip`** `boolean` (default: `true`) — Whether the tooltip moves to the opposite side of its trigger when there is not enough room on the requested one
 
 ### Base Properties
 
@@ -214,14 +214,22 @@ function ControlledExample() {
 
 ### Conditional Tooltip
 
-Show a tooltip only when certain conditions are met:
+Show a tooltip only when certain conditions are met. Empty content (`null`, `undefined` or `''`) turns the tooltip off: nothing opens and the trigger gets no `aria-describedby`.
 
 ```jsx
-<TooltipProvider title={hasError ? "Fix errors first" : null}>
-  <Button isDisabled={hasError}>Submit</Button>
+<TooltipProvider title={isShared ? 'Visible to your whole team' : null}>
+  <Button>Share</Button>
 </TooltipProvider>
 ```
 
+A disabled `Button` receives neither hover nor focus, so a `TooltipProvider` around it never opens. Give the button its own `tooltip` instead; it then stays hoverable and focusable while disabled:
+
+```jsx
+<Button isDisabled={hasError} tooltip={hasError ? 'Fix errors first' : undefined}>
+  Submit
+</Button>
+```
+
 ### Focus-Only Trigger
 
 Show tooltip only on focus, not on hover:
@@ -238,7 +246,10 @@ Show tooltip only on focus, not on hover:
 
 - `Tab` - Moves focus to the trigger element, showing the tooltip after the delay
 - `Shift + Tab` - Moves focus away from the trigger, hiding the tooltip
+- `Escape` - Hides the tooltip
 - Tooltips automatically appear on focus for keyboard users
+- Pressing the trigger hides the tooltip, unless `shouldCloseOnPress` is `false`
+- When the page or an element containing the trigger scrolls, the tooltip follows the trigger while it stays in view, and hides once it is scrolled out of view
 
 ### Screen Reader Support
 
@@ -249,7 +260,7 @@ Show tooltip only on focus, not on hover:
 
 ### ARIA Properties
 
-- `aria-describedby` - Automatically set on the trigger to reference the tooltip
+- `aria-describedby` - Automatically set on the trigger to reference the tooltip while it is open. `Button`, `ItemBadge`, `ItemAction`, `Checkbox`, `Radio` and `Item` rows (`ItemButton`, list and menu items) add it after their own `aria-describedby` rather than replacing it
 - All standard ARIA labeling props are supported
 
 ### Best Practices

package/docs/components/overlays/TooltipTrigger.md

@@ -24,6 +24,8 @@ Lower-level component that wraps a trigger element and a `Tooltip`. Use when you
 - **`trigger`** `'focus'` — When set, opens the tooltip only on focus instead of both focus and hover
 - **`shouldCloseOnPress`** `boolean` (default: `true`) — Whether the tooltip closes when the trigger is pressed
 
+A `Tooltip` with empty content (`null`, `undefined` or `''`) never opens. When the page or an element containing the trigger scrolls, an open tooltip follows its trigger while the trigger stays in view, and closes once it is scrolled out of view. Set `shouldFlip` on the `Tooltip` itself.
+
 ### Base Properties
 
 Supports [Base properties](../../BaseProperties.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cube-dev/ui-kit",
-  "version": "0.194.1",
+  "version": "0.196.0",
   "type": "module",
   "description": "UIKit for Cube Projects",
   "repository": {