> To build a Wix site agentically, or add Wix features like bookings or a store to a site you already have, follow https://www.wix.com/headless/skill.md
> 
> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - If a reference page seems to be missing its schema (parameters, return types, or type definitions), append `?schema=true` to its `.md` URL (e.g. `https://dev.wix.com/docs/contexts/contexts/stores/category-info/use-category-info-context.md?schema=true`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Input Component

## Article: Input Component

## Article Link: https://dev.wix.com/docs/wix-design-system/components/form/input-component.md

## Article Content:

# Input

_Components/Form_

Interactive docs page: <https://wix-pages.com/design-system-documentation/#/component/input>

## Overview

```jsx
<Box align="center">
  <Box direction="vertical" width="30%">
    <FormField label="Name">
      <Input />
    </FormField>
  </Box>
</Box>;
```

Inputs let users enter short values into a text field. It can be used for forms and tables, or to build other form components like `<AutoComplete/>` or `<NumberInput/>`.

### Do

- Use it to insert names, titles, addresses, and other areas where users will enter short bits of text.
- Use it to build custom input fields.

### Don't

- Don't use it to insert long paragraphs. Use the `<InputArea/>` component instead.
- Don't use it as a search input. Use the `<Search/>` component instead.

### Feature examples

#### Size

Adjust the size of the input using the `size` prop. It supports 3 sizes:

- For most common cases, use the default `medium.`
- To emphasize specific inputs in onboarding flows, use `large`.
- Use `small` for more compact layout.
- Rely of `tiny` size for very compact layouts, use this size sparingly.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <Input size="large" placeholder="Large" />
  <Input size="medium" placeholder="Medium" />
  <Input size="small" placeholder="Small" />
  <Input size="tiny" placeholder="Tiny" />
</StorybookComponents.Stack>;
```

#### Border

Style the input using the `border` prop. It supports 4 styles:

- For forms and most common cases, use `standard`.
- To build inputs that can be used to filter data, use `round`.
- Use `bottomLine` to create an editable, underlined title field.
- When a component provides its own hover and focus styles, such as a table or spreadsheet cells, use `none`.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <Input border="standard" placeholder="Standard" />
  <Input border="round" placeholder="Round" />
  <Input border="bottomLine" placeholder="Bottom line" />
  <Input border="none" placeholder="None" />
</StorybookComponents.Stack>;
```

#### Status

Control the status of the input using the `status` prop. It supports 3 states:

- `error` demonstrates that a required input is missing something or the entry was invalid.
- `warning` highlights an input value that might have a significant impact to a user.
- `loading` shows when an input value is being uploaded to the server.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <Input status="error" placeholder="Error" />
  <Input status="warning" placeholder="Warning" />
  <Input status="loading" placeholder="Loading" />
</StorybookComponents.Stack>;
```

#### Status message

Add text that explains the status or what action the user should take with the `statusMessage` prop.

Showing the status message inline, directly below the input is preferred in all default cases.

- To add an accessible inline message, wrap the component in a `<FormField/>` and add the `statusMessage`.
- To add a status message in a tooltip that requires users to hover on the icon, use the `statusMessage` prop. Control tooltip placement with `tooltipPlacement` prop.

View more inline status message examples in `<FormField/>`.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <StorybookComponents.Stack flexDirection="column" gap="12px">
    <Text secondary>For all default cases:</Text>
    <FormField status="error" statusMessage="This is an error message.">
      <Input placeholder="See message below" />
    </FormField>
  </StorybookComponents.Stack>
  <StorybookComponents.Stack flexDirection="column" gap="12px">
    <Text secondary>For narrow layouts only:</Text>
    <Input
      placeholder="Hover on status icon"
      status="error"
      statusMessage="This is an error message."
      tooltipPlacement="top-end"
    />
  </StorybookComponents.Stack>
</StorybookComponents.Stack>;
```

#### Read-only and disabled

Inputs can also be made read-only or disabled entirely.

- `readOnly` disables adding or editing, but allows the user to copy the current value. Use it to display URLs, code, etc.
- `disabled`removes all interactions and creates a disabled input state. Use it to highlight functions that are unavailable.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <Input readOnly value="Read-only" />
  <Input disabled value="Disabled" />
</StorybookComponents.Stack>;
```

#### Prefix & suffix

Add text, icons or a button at the beginning or end of a text field using `prefix` and `suffix`.

```jsx
<StorybookComponents.Stack flexDirection="column">
  <Input
    prefix={<Input.Affix>https://</Input.Affix>}
    suffix={<Input.Affix>.com</Input.Affix>}
    value=""
  />
  <Input
    prefix={
      <Input.IconAffix>
        <Icons.GitHub />
      </Input.IconAffix>
    }
    suffix={
      <Input.IconAffix>
        <TextButton>Button</TextButton>
      </Input.IconAffix>
    }
    value=""
  />
</StorybookComponents.Stack>;
```

#### Clear button

Enable a button that lets users easily clear the input value by using the `clearButton` prop.

```jsx
() => {
  const [inputText, setInputText] = React.useState(
    'Click the clear button to erase this value.',
  );

  return (
    <Input
      value={inputText}
      clearButton
      onChange={(e) => setInputText(e.target.value)}
      onClear={() => setInputText('')}
    />
  );
};
```

#### Text overflow

Control long text values with the `textOverflow` prop. There are 2 options:

- `clip` (the default) cuts off text that is longer than the input field.
- `ellipsis` truncates the additional text with an ellipsis. This is especially useful with the `bottomLine` input style.

```jsx
<Input
  textOverflow="ellipsis"
  border="bottomLine"
  value="This is an extremely long sentence that takes up far more space than can fit inside this input field, so it has to be shortened so that the beginning can be read, but with an ellipsis to indicate there is more text than can be shown at once."
/>;
```

#### Text direction

`rtl` controls the text direction and layout behavior of the `Input`.

- `{false}` (default): renders input in LTR mode.
- `{true}` renders input in RTL mode

```jsx
() => (
  <Box gap="20px" direction="vertical">
    <FormField label="LTR (default)">
      <Input rtl={false} defaultValue="Left to right text" />
    </FormField>

    <FormField label="RTL">
      <Input rtl defaultValue="טקסט מימין לשמאל" />
    </FormField>
  </Box>
);
```

#### On-stage input color

Since updating Business Manager to use Harmony theme, there has been added a new input background color. You can change it using `backgroundColor` property.

**Important**: this is only applicable to Harmony theme, on-stage color is always fixed to `--wds-input-background-fill-on-stage`

```jsx
() => (
  <Box direction="vertical" gap="24px">
    <Box direction="vertical" width="30%">
      <FormField label="On-stage background">
        <Input
          placeholder="Enter your name"
          backgroundColor="var(--wds-input-background-fill-on-stage)"
        />
      </FormField>
    </Box>
    <Box direction="vertical" width="30%">
      <FormField label="Default background">
        <Input placeholder="Enter your name" />
      </FormField>
    </Box>
  </Box>
);
```

### Developer examples

#### Masked Input using use-mask-input

_Requires use of external package. In this example `use-mask-input` package is used._

```jsx
() => {
  const { withMask } = require('use-mask-input');
  const maskRef = React.useMemo(
    () =>
      withMask('AA99 AAA', {
        placeholder: '_',
        showMaskOnHover: false,
      }),
    [],
  );
  return <Input placeholder="AB12 CDE" inputRef={maskRef} />;
};
```

#### Masked Input using react-imask

_Requires use of external package. In this example `react-imask` package is used._

```jsx
() => {
  const { IMaskInput } = require('react-imask');

  const CardMaskInput = React.forwardRef((props, ref) => (
    <IMaskInput
      {...props}
      mask="0000 0000 0000 0000"
      inputRef={ref}
      placeholderChar="_"
      lazy={false}
    />
  ));

  // `autoSelect={false}` so focusing doesn't highlight the mask's
  // placeholder characters (with `lazy: false` they live in `input.value`).
  return (
    <Input
      placeholder="1234 5678 9012 3456"
      customInput={CardMaskInput}
      autoSelect={false}
    />
  );
};
```

### Common use case examples

#### Compound input

When multiple inputs represent the same kinds of data, like phone numbers or addresses, fields can be shown together under a single title using the `<Layout/>` component.

```jsx
() => {
  const [value, setValue] = React.useState('');

  const getDisplayValue = (value) => {
    const [, group1, group2, group3] = value
      .replace(/\D/g, '')
      .match(/(\d{0,2})(\d{0,3})(\d{0,4})/);
    return (
      (!group2 ? group1 : group1 + ' ') + group2 + (group3 ? '-' + group3 : '')
    );
  };

  const options = [
    listItemSelectBuilder({ id: 0, title: 'Israel', suffix: '+972' }),
    listItemSelectBuilder({ id: 1, title: 'Japan', suffix: '+81' }),
    listItemSelectBuilder({ id: 2, title: 'Australia', suffix: '+61' }),
  ];

  const onChange = (e) => {
    const { value } = e.target;
    if (value.length < 12) {
      setValue(getDisplayValue(value));
    }
  };

  const renderAutoComplete = () => (
    <AutoComplete
      popoverProps={{ placement: 'bottom-start' }}
      value="+972"
      options={options}
    />
  );

  return (
    <FormField label="Phone number">
      <Layout gap={6}>
        <Cell span={2}>{renderAutoComplete()}</Cell>
        <Cell span={10}>
          <Input placeholder="00 000-0000" onChange={onChange} value={value} />
        </Cell>
      </Layout>
    </FormField>
  );
};
```

#### Input as a title

Inputs can also be used as card titles to help organize groups and files. This works best with the `bottomLine` border.

```jsx
() => {
  const renderCard = (imageSrc, inputValue) => (
    <Card>
      <Box direction="vertical" padding="SP1 SP1 SP2">
        <Layout gap={12}>
          <Cell>
            <Box padding="6px 6px 0px">
              <Image borderRadius="4px" height="180px" src={imageSrc} />
            </Box>
          </Cell>

          <Cell>
            <Input
              border="bottomLine"
              textOverflow="ellipsis"
              defaultValue={inputValue}
            />
          </Cell>
        </Layout>
      </Box>
    </Card>
  );

  return (
    <Layout>
      <Cell span={6}>{renderCard('', 'Empty photo album')}</Cell>
      <Cell span={6}>{renderCard('example.jpg', 'Cooking recipes album')}</Cell>
    </Layout>
  );
};
```

## Code

```jsx
import { Input } from '@wix/design-system';
```

### Props

| Name | Type | Default | Description |
| --- | --- | --- | --- |
| `ariaControls` | `string` | — | Associate a control with the regions that it controls. |
| `ariaDescribedby` | `string` | — | Associate a region with its descriptions. Similar to aria-controls but instead associating descriptions to the region and description identifiers are separated with a space. |
| `ariaLabel` | `string` | — | Define a string that labels the current element in case where a text label isn't visible on the screen. |
| `ariaRoledescription` | `string` | — | Sets the `aria-roledescription` attribute of the `<input>` element, giving assistive technologies a readable description of its role. |
| `autocomplete` | `string` | — | Sets the value of the native `autocomplete` attribute, for example `off` or `email`. |
| `autoFocus` | `boolean` | — | Focus the element on mount (standard React input autoFocus) |
| `autoSelect` | `boolean` | — | Automatically selects the entire input text. |
| `backgroundColor` | `string` | — | Sets the background color of the input. Accepts any CSS color value. |
| `border` | `"none" \| "standard" \| "round" \| "bottomLine"` | — | Control the border style of input. |
| `children` | `ReactNode` | — |  |
| `clearButton` | `boolean` | — | Displays clear button (X) on a non-empty input. |
| `clearButtonAriaLabel` | `string` | — | Aria label for the clear button. |
| `clearButtonTooltipContent` | `ReactNode` | — | When provided, hovering displays a tooltip with this content. |
| `clearButtonTooltipProps` | `TooltipCommonProps` | — | Clear button tooltip props. |
| `customInput` | `ReactNode \| Function` | — | Render a custom input instead of the default html input tag. |
| `dataHook` | `string` | — | Applies a data-hook HTML attribute that can be used in the tests. |
| `defaultValue` | `string \| number` | — | Defines the initial value of an input. |
| `disabled` | `boolean` | — | Specifies whether input should be disabled or not. |
| `disableEditing` | `boolean` | — | Restricts input editing. |
| `enterKeyHint` | `"search" \| "enter" \| "done" \| "go" \| "next" \| "previous" \| "send"` | — | Sets the label of the virtual keyboard's enter key on touch devices. |
| `focusOnClearClick` | `boolean` | — | Specifies whether to focus the field when clear button is clicked. |
| `hideStatusSuffix` | `boolean` | — | Specifies whether status suffix should be hidden. |
| `id` | `string` | — | Assigns a unique identifier for the root element. |
| `inputmode` | `string` | — | Sets the value of the native `inputmode` attribute, which tells mobile browsers which on-screen keyboard to show, for example `numeric` or `email`. |
| `inputRef` | `null \| (instance: HTMLInputElement \| null) => void \| RefObject<HTMLInputElement>` | — | Ref to the underlying `<input>` DOM element. Accepts callback and object refs. Use for input masking libraries such as `use-mask-input`. Memoize callback refs to avoid reattaching on every render. |
| `max` | `number` | — | Sets a maximum value of an input. Similar to html5 max attribute. |
| `maxLength` | `number` | — | Sets the maximum number of characters that can be inserted to a field. |
| `menuArrow` | `boolean` | — | Specifies whether input should have a dropdown menu arrow on the right side. |
| `min` | `number` | — | Sets a minimum value of an input. Similar to HTML5 min attribute. |
| `name` | `string` | — | Reference element data when a form is submitted. |
| `noLeftBorderRadius` | `boolean` | — | Specifies whether input shouldn't have rounded corners on its left. |
| `noRightBorderRadius` | `boolean` | — | Specifies whether input shouldn't have rounded corners on its right. |
| `onBlur` | `FocusEventHandler` | — | Defines a standard input onBlur callback. |
| `onChange` | `ChangeEventHandler` | — | Defines a standard input onChange callback. |
| `onClear` | `(event: KeyboardEvent<HTMLButtonElement> \| MouseEvent<HTMLButtonElement, MouseEvent>) => void` | — | Displays clear button (X) on a non-empty input and calls a callback function. |
| `onCompositionChange` | `(isComposing: boolean) => void` | — | Defines a callback function called on compositionstart/compositionend events. |
| `onCopy` | `ClipboardEventHandler<HTMLInputElement>` | — | Defines a callback handler that is called when user copies text to a clipboard (using a mouse or keyboard shortcut) |
| `onEnterPressed` | `KeyboardEventHandler<HTMLInputElement>` | — | Defines a callback handler that is called when the user presses -enter-. |
| `onEscapePressed` | `KeyboardEventHandler<HTMLInputElement>` | — | Defines a callback handler that is called when the user presses -escape-. |
| `onFocus` | `FocusEventHandler` | — | Defines a standard input onFocus callback. |
| `onInputClicked` | `MouseEventHandler` | — | Defines a standard input onClick callback. |
| `onKeyDown` | `KeyboardEventHandler<HTMLInputElement>` | — | Defines a standard input onKeyDown callback. |
| `onKeyUp` | `KeyboardEventHandler<HTMLInputElement>` | — | Defines a standard input onKeyUp callback. |
| `onPaste` | `ClipboardEventHandler<HTMLInputElement>` | — | Defines a callback handler that is called when user pastes text from a clipboard (using a mouse or keyboard shortcut) |
| `pattern` | `string` | — | Sets a pattern that typed value must match to be valid (regex) |
| `placeholder` | `string` | — | Sets a placeholder message to display. |
| `prefix` | `ReactNode` | — | Pass a component you want to show as the prefix of the input, e.g., text, icon. |
| `readOnly` | `boolean` | — | Specifies whether input is read only. |
| `ref` | `null \| string \| (instance: InputImperativeActions \| null) => void \| RefObject<InputImperativeActions>` | — | Allows getting a ref to the component instance. Once the component unmounts, React will set `ref.current` to `null` (or call the ref with `null` if you passed a callback ref). |
| `required` | `boolean` | — | Specifies whether input is mandatory. |
| `role` | `string` | — | Specifies the role of the input element for accessibility. |
| `rtl` | `boolean` | — | Specifies text direction. If true, the text is displayed from right to left. |
| `size` | `"small" \| "tiny" \| "medium" \| "large"` | — | Controls the size of the input. Default value: `medium` |
| `status` | `"error" \| "warning" \| "loading"` | — | Specify the status of a field. |
| `statusMessage` | `ReactNode` | — | Defines the message to display on status icon hover. If not given or empty, no tooltip is displayed. |
| `statusMessageTooltipProps` | `TooltipCommonProps` | — | Status message tooltip props. |
| `step` | `number` | — | Specifies the interval between number values. |
| `suffix` | `ReactNode` | — | Pass a component you want to show as the suffix of the input, e.g., text, icon. |
| `tabIndex` | `number` | — | Indicates that element can be focused and where it participates in sequential keyboard navigation. |
| `textOverflow` | `"ellipsis" \| "clip"` | — | Handles text overflow behavior. It can either `clip` (default) or display `ellipsis`. |
| `tooltipPlacement` | `"right" \| "left" \| "top" \| "bottom" \| "auto" \| "auto-start" \| "auto-end" \| "top-start" \| "top-end" \| "right-start" \| "right-end" \| "bottom-end" \| "bottom-start" \| "left-end" \| "left-start"` | — | Controls placement of a status tooltip. |
| `type` | `string` | — | Specifies the type of `<input/>` element to display. Default is text. |
| `value` | `string \| number` | — | Specifies the current value of the element. |
| `withSelection` | `boolean` | — |  |

## Testkit

Import the driver matching your test environment:

```jsx
// UniDriver
import { InputUniDriver } from '@wix/design-system/dist/testkit/unidriver';

// Vanilla
import { InputTestkit } from '@wix/design-system/dist/testkit';

// Puppeteer
import { InputTestkit } from '@wix/design-system/dist/testkit/puppeteer';

// Testing Library
import { InputTestkit } from '@wix/design-system/dist/testkit/testing-library';
```

### Driver methods

| Method | Description |
| --- | --- |
| `click` | — |
| `getInputAttribute` | — |
| `getInputElementClasses` | — |
| `suffixComponentExists` | — |
| `getRootElementClasses` | — |
| `getAriaDescribedby` | — |
| `getAriaLabel` | — |
| `getName` | — |
| `getMaxLength` | — |
| `getType` | — |
| `getAriaControls` | — |
| `clickIconAffix` | — |
| `clickCustomAffix` | — |
| `getCustomAffixText` | — |
| `hasSuffix` | — |
| `getClearButtonTooltipContent` | — |
| `prefixComponentExists` | — |
| `hasPrefix` | — |
| `hasClearButton` | — |
| `clickClear` | — |
| `getValue` | — |
| `getText` | — |
| `getPattern` | — |
| `getPlaceholder` | — |
| `isOfSize` | — |
| `getSize` | — |
| `isDisabled` | — |
| `isHoveredStyle` | — |
| `isFocusedStyle` | — |
| `getRequired` | — |
| `enterText` | — |
| `getAutocomplete` | — |
| `getDefaultValue` | — |
| `getTabIndex` | — |
| `isCustomInput` | — |
| `getReadOnly` | — |
| `getDisabled` | — |
| `getTextOverflow` | — |
| `focus` | — |
| `blur` | — |
| `keyUp` | — |
| `keyDown` | — |
| `pressKey` | — |
| `paste` | — |
| `copy` | — |
| `wheel` | — |
| `trigger` | — |
| `isFocus` | — |
| `clickMenuArrow` | — |
| `hasMenuArrow` | — |
| `isRTL` | — |
| `getCursorLocation` | — |
| `clearText` | — |
| `clickOutside` | — |
| `isMasked` | — |
| `isSelected` | — |
| `hasStatus` | Return true if there's a status |
| `getStatusMessage` | If there's a status message, returns its text value |
| `exists` | Checks whether the component found with the given data hook. |
| `element` | Gets the component root element. |
| `base` | Returns UniDriver for the base element. |

## Changelog

- **1.339.0** (2026-10-19) — maintenance release, no component-specific changes
- **1.338.0** (2026-10-15) — maintenance release, no component-specific changes
- **1.336.0** (2026-10-13) — fix: the ticker up/down arrows follow the icon theme, so Harmony (odeditor) shows its own chevrons. ([#17155](invalid-url))
- **1.331.0** (2026-10-01) — maintenance release, no component-specific changes
- **1.330.3** (2026-09-29) — maintenance release, no component-specific changes
- **1.330.1** (2026-09-28) — fix: the `inputmode` prop now reaches the input, so NumberInput shows the numeric keyboard on mobile. GoogleAddressInput without a `value` now keeps typed text and shows address suggestions. ([#17261](invalid-url))
- **1.330.0** (2026-09-28) — maintenance release, no component-specific changes
- **1.328.0** (2026-09-22) — maintenance release, no component-specific changes
- **1.326.0** (2026-09-17) — maintenance release, no component-specific changes
- **1.325.0** (2026-09-17) — maintenance release, no component-specific changes
- **1.323.0** (2026-09-10) — maintenance release, no component-specific changes
- **1.320.1** (2026-09-04) — fix: restore the pre-restyle read-only appearance (grey fill, visible border, full-contrast value, undimmed FormField label) in consumers that load no design-token theme, such as the old Business Manager theme. Every token theme is untouched: the read-only rules resolve through the same theme tokens the default state already uses, so only the token-less fallbacks change. ([#16957](invalid-url)) — has visual changes
- **1.317.0** (2026-08-26) — fix: in Harmony (odeditor), read-only inputs no longer show a hover fill and their value text renders muted, and a FormField label above a read-only or disabled Input renders in the disabled color. ([#16858](invalid-url)) — has visual changes
- **1.312.0** (2026-08-14) — maintenance release, no component-specific changes
- **1.310.0** (2026-08-10) — maintenance release, no component-specific changes
- **1.292.0** (2026-06-22) — maintenance release, no component-specific changes
- **1.291.0** (2026-06-19) — fix: clear button no longer opens the dropdown options ([#16421](invalid-url))
- **1.289.0** (2026-06-17) — maintenance release, no component-specific changes
- **1.288.0** (2026-06-15) — maintenance release, no component-specific changes
- **1.279.0** (2026-05-13) — maintenance release, no component-specific changes
- **1.278.0** (2026-05-08) — maintenance release, no component-specific changes
- **1.277.0** (2026-05-07) — maintenance release, no component-specific changes
- **1.273.0** (2026-04-30) — maintenance release, no component-specific changes
- **1.272.0** (2026-04-27) — maintenance release, no component-specific changes
- **1.266.0** (2026-04-07) — maintenance release, no component-specific changes
- **1.263.0** (2026-03-31) — maintenance release, no component-specific changes
- **1.260.0** (2026-03-17) — maintenance release, no component-specific changes
- **1.254.0** (2026-02-03) — maintenance release, no component-specific changes
- **1.247.2** (2026-01-21) — maintenance release, no component-specific changes
- **1.242.0** (2025-12-19) — maintenance release, no component-specific changes
- **1.241.0** (2025-12-17) — maintenance release, no component-specific changes
- **1.232.0** (2025-11-28) — maintenance release, no component-specific changes
- **1.228.0** (2025-11-18) — fix: use tokens for autofilled state ([#15520](invalid-url))
- **1.224.0** (2025-10-30) — maintenance release, no component-specific changes
- **1.220.2** (2025-10-06) — fix: stop using specific UniDrivers to not force consumers to install transitional deps ([#15385](invalid-url))
- **1.220.0** (2025-09-29) — maintenance release, no component-specific changes
- **1.217.0** (2025-09-08) — breaking: remove background and border when border is none or bottomLine ([#15284](invalid-url))
- **1.214.2** (2025-08-25) — maintenance release, no component-specific changes
- **1.213.0** (2025-08-19) — maintenance release, no component-specific changes
- **1.212.0** (2025-08-11) — maintenance release, no component-specific changes
- **1.209.0** (2025-07-30) — fix: `isDisabled` driver testkit method ([#15140](invalid-url))
- **1.208.0** (2025-07-25) — maintenance release, no component-specific changes
- **1.207.0** (2025-07-24) — maintenance release, no component-specific changes
- **1.204.1** (2025-07-10) — maintenance release, no component-specific changes
- **1.202.0** (2025-06-27) — maintenance release, no component-specific changes
- **1.200.0** (2025-06-17) — feat: expose `input` DOM node via imperative handle ([#14936](invalid-url))
- **1.188.1** (2025-05-14) — maintenance release, no component-specific changes
- **1.184.0** (2025-04-30) — maintenance release, no component-specific changes
- **1.175.1** (2025-04-01) — maintenance release, no component-specific changes
- **1.172.1** (2025-03-21) — maintenance release, no component-specific changes
- **1.167.0** (2025-03-05) — breaking: change menu Arrow Icon color in studio theme ([#14579](invalid-url))
- **1.165.0** (2025-02-27) — feat: expose onCopy ([#14563](invalid-url))
- **1.155.0** (2025-01-23) — maintenance release, no component-specific changes
- **1.149.1** (2024-12-20) — fix: fix attribute based testkit methods ([#14412](invalid-url))
- **1.149.1** (2024-12-20) — fix: fix testkit disabled flagging ([#14413](invalid-url))
- **1.149.1** (2024-12-20) — fix: revert to previous `autoSelect` and `autoFocus` behavior ([#14406](invalid-url))
- **1.147.0** (2024-12-13) — maintenance release, no component-specific changes
- **1.139.2** (2024-11-12) — maintenance release, no component-specific changes
- **1.138.1** (2024-10-30) — maintenance release, no component-specific changes
- **1.129.0** (2024-09-25) — maintenance release, no component-specific changes
- **1.128.0** (2024-09-19) — maintenance release, no component-specific changes
- **1.127.1** (2024-09-16) — maintenance release, no component-specific changes
- **1.115.0** (2024-07-17) — maintenance release, no component-specific changes
- **1.114.0** (2024-07-11) — feat: expose status message tooltip props ([#13917](invalid-url))
- **1.109.2** (2024-06-17) — maintenance release, no component-specific changes
- **1.107.0** (2024-05-29) — maintenance release, no component-specific changes
- **1.106.0** (2024-05-24) — maintenance release, no component-specific changes
- **1.104.1** (2024-05-14) — fix: fix clear button misalignment ([#13717](invalid-url))
- **1.102.0** (2024-04-16) — maintenance release, no component-specific changes
- **1.97.2** (2024-03-04) — feat: inputAffix testkit bug fix & Input testkit new method ([#13415](invalid-url))
- **1.97.0** (2024-02-26) — maintenance release, no component-specific changes
- **1.92.1** (2024-02-05) — maintenance release, no component-specific changes