Skip to content

Textarea

Alpha
Use Textarea for multi-line text input form fields
import {Textarea} from '@primer/react'

Examples

Textarea components must always be accompanied by a corresponding label to improve support for assistive technologies. Examples below are provided for conciseness and may not reflect accessibility best practices.

Use the FormControl component to render a Textarea with a corresponding label.

Controlled mode

Uncontrolled mode

Displaying form validation state

Inactive

Resize

By default, Textarea can be resized by the user vertically and horizontally. Resizing can be prevented by setting resize to none

Custom styling

Props

Textarea

NameTypeDefaultDescription
required
boolean
Indicates to the user and assistive technologies that the field value is required
cols
number
Specifies the visible width of a text area.
rows
number
Specifies the visible height of a text area.
block
boolean
falseExpands with width of the component to fill the parent elements
resize
'both' | 'horizontal' | 'vertical' | 'none'
'both'Changes background color to a higher contrast color
validationStatus
'success' | 'error' | undefined
Style the textarea to match the current form validation status
ref
React.RefObject<HTMLTextAreaElement>
A ref to the element rendered by this component.
sx
SystemStyleObject
Style overrides to apply to the component. See also overriding styles.
ref
React.RefObject<HTMLTextareaElement>
A ref to the element rendered by this component.
Additional props are passed to the <input> element. See MDN for a list of props accepted by the <input> element.

Status

Alpha

  • Component props are documented on primer.style/react.
  • Component does not have any unnecessary third-party dependencies.
  • Component can adapt to different themes.
  • Component can adapt to different screen sizes.
  • Component has 100% test coverage.

Beta

  • Component is used in a production application.
  • Common usage examples are documented on primer.style/react.
  • Common usage examples are documented in storybook stories.
  • Component has been reviewed by a systems designer and any resulting issues have been addressed.
  • Component has been manually reviewed by the accessibility team and any resulting issues have been addressed.

Stable

  • Component API has been stable with no breaking changes for at least one month.
  • Feedback on API usability has been sought from developers using the component and any resulting issues have been addressed.
  • Component has corresponding design guidelines documented in the interface guidelines.
  • Component has corresponding Figma component in the Primer Web library.
Edit this page on GitHub
2 contributorsmperrottirezrah
Last edited by mperrotti on July 20, 2022