Textarea is Clementine DS’s multi-line free-text input. It wraps Mantine’s Textarea component and re-exports it with Clementine token bindings applied through ClementineDSProvider. Every prop that Mantine’s Textarea accepts is available — import from @clementine-ds/ui, not from @mantine/core directly.
Use Textarea when you expect users to enter more than one line of plain text: comments, notes, descriptions, or free-form messages. For single-line input use TextInput. For rich text, reach for a rich-text editor (not yet in this DS).
When to use
- The expected input spans multiple lines — a comment, a bio, a product description, a support message.
- You want to give users a visible writing area that clearly signals “this field accepts long content.”
- You need fixed row height with optional user resize, or auto-growing height that tracks content.
- The field needs a character counter displayed inside the input boundary.
When not to use
- Single-line values — use
TextInput. The extra vertical space of aTextareacreates a misleading affordance for short values. - Rich text with formatting — a
Textarearenders plain text only. Use a rich-text editor for Markdown, HTML, or formatted content. - Structured multi-part input — if the user must fill in several distinct fields, use multiple
TextInputcomponents instead of one largeTextarea.
Usage
Controlled usage
Character counter with bottomSection
Uncontrolled usage with FormData
Props
TextareaProps extends Mantine’s TextareaProps directly — all Mantine props are available. The table below covers the props you’ll use most often.
Interaction states
Textarea shares the same interaction-state model as TextInput, with one fewer state — there is no loading spinner position difference.
Token contract
These design tokens coverTextarea. Tokens resolve through semantic aliases into the Clementine primitive palette.
Accessibility
- Always supply a visible
labelprop. Usearia-labelonly when no visible label is possible. - On error, Mantine sets
aria-invalid="true"on the textarea and associates the error element viaaria-describedby. Verify this wiring in your form before shipping. - Preserve user-controlled resize (
resize="vertical") unless the layout specifically cannot accommodate a taller textarea. Removing resize is a regression for users who enlarge text or have motor differences. - The
requiredprop sets the nativerequiredattribute, which screen readers announce. If you usewithAsteriskfor visual-only indication, also communicate the requirement through thedescriptionprop. Textareasupports standard keyboard interactions —Tabto focus,Shift+Tabto move backwards, and all standard text-editing keys inside the field.
Draft status
Textarea carries a Draft status as of clementine-ds@HEAD (2026-06-08). The following items are still open:
- Resize default — it is undecided whether the default behavior should be fixed rows with user resize, or auto-grow to content. Until resolved, use
resize="vertical"orautosizeexplicitly rather than relying on any default. - Character counter strategy — it is undecided whether a counter should appear automatically when
maxLengthis set, or only whenbottomSectionis used explicitly. UsebottomSectionfor now. - Token values (
textarea.border.hover,textarea.fg.disabled,textarea.radius) are defined in the spec but not yet validated against the rendered output.