Text area

Visitors usually see single-line fields for search and short answers. Long copy on pages comes from the WYSIWYG component or similar. Authors enter longer strings in component dialogs (for example descriptions) using dialog text areas where the field is plain text.

• Browser text areas can often be resized by the user unless disabled.
• Validation messages should appear near the field and describe what to fix.

1. Label that names the field.
2. Multi-line input area.
3. Optional hint or error text below the field.

Replace with a labelled text area and optional hint line.

• Set character limits that match real needs (not arbitrary short caps).
• For author dialogs, match field labels to how content will appear on the page.

Do

• Provide rows, max length, and hint text when you add public forms.
• Validate on the server and, where helpful, on the client for length and safety.

Don't

• Don't block paste without a strong reason.

• Authors: Long plain text in a component dialog when rich text is not required.
• Visitors: Only when a flow truly needs free-form multi-line input (often custom forms; follow security and privacy review).

• Short answers; use a single-line field.
• Formatted marketing copy; use WYSIWYG.