Text Areas

A text area is the multi-line field people write into (a comment, a chat message, a prompt, an issue description) together with the controls that sit around it. The three blocks in this family are three different jobs for the same box: a composer that tags people, a prompt field with attachment and model pickers under it, and a tabbed editor with formatting along the foot.

Enter is the contested key. In a chat composer Enter sends and Shift+Enter breaks the line; in an editor Enter must always break the line and sending belongs to the button. The component cannot guess which it is, so decide early and label it near the send control, because the person who learns the wrong one learns it by posting half a sentence. Height is the other decision: start at one line, grow with the content up to a ceiling and scroll after that. A tall empty box does nothing for the common case and pushes the footer controls off the reader's screen.

8 blocks

Tagging composer

Chat and comment fields that mention people: the tagged names sit above, the pill takes the message

Tagging composer, audience

A message box that says who will be notified, and lets you mute or drop them

Tagging composer, thread

A team channel: grouped messages over a tray composer that tags people

Prompt field

An AI composer with a hint in the strip: connect Figma, files above the text, web, model and depth, voice, send

Prompt field, ink

A prompt field whose tools ride in one ink pill, and voice morphs it into the recorder

Prompt field, context

A prompt where you can see everything the model will read, and how full its window is

Tabbed editor

Issue and task editors: one field per section, each keeping its draft, with formatting underneath

Tabbed editor, template

An issue editor where every section starts as a sentence with blanks

01

Using Text Areas

Reach for it when

  • Input that might be one line or twenty: comments, replies, messages
  • Composers that carry attachment, model or mode controls beneath the field
  • Issue and task editors that need light formatting and nothing more
  • Anywhere people paste several paragraphs at once

Reach for something else when

  • A short single value like a name or a subject: a one-line input keeps the form's rhythm
  • Documents with headings, tables and images. That is a rich editor's job
  • Several values typed into one box: a tag input keeps them separable afterwards
02

Where it shows up

01

Chat composers

A message field that holds the people you have tagged as chips above it, an attachment control beside it, and a send that only lights once there is something to send.

02

AI prompt fields

An assistant's input, where most of the interface sits underneath the box: what to attach, whether to search the web, which model, which mode, and dictation for people who would rather talk.

03

Issue and task editors

A tracker's editor, with tabs over one field so description and details share a box, and enough formatting along the bottom for a code reference and a bulleted repro without becoming a document tool.

04

Inline review comments

A field that opens in place against the thing being discussed, grows as the argument gets longer, and keeps its submit reachable instead of pushing it off the bottom of a panel.

03

Questions

Should Enter send the message or insert a line break?

It depends what the field is. In a chat or comment composer, Enter sends and Shift+Enter breaks the line, because most messages are one line and reaching for a button every time is slow. In an editor where paragraphs are normal, Enter must break the line and sending belongs to a button. Whichever you choose, say so next to the control.

Should a text area grow with its content or scroll?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.