The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.See #1493324: Inline form errors for accessibility and UX
Below is an example of the properly themed inline error messages.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | support_inline_error-2548187-9.patch | 5.01 KB | s_leu |
| #9 | support_inline_error-2548187-9.interdiff.txt | 1.53 KB | s_leu |
| #4 | Screen Shot 2015-08-08 at 8.00.04 PM.png | 12.99 KB | neardark |
| #3 | support_inline_error-2548187-3.patch | 3.49 KB | neardark |
Comments
Comment #2
neardark commentedComment #3
neardark commentedI've used the bootstrap class text-danger to denote inline error messages. This patch also works with the Drupal Bootstrap setting for setting required fields to immediately show an error message and clear upon input. However, this doesn't work with ckEditor fields. This will be addressed in #2548189: Support inline error messages for ckEditor fields
Comment #4
neardark commentedComment #5
neardark commentedComment #6
neardark commentedComment #7
neardark commentedComment #8
neardark commentedSetting this to needs work as some select items are failing, such as Radios/Checkboxes.
Comment #9
s_leu commentedHere's a patch that also considers fields with checkboxes/radios widgets.
Comment #10
markhalliwellPretty sure this related issue/commits fixed this. If not, please re-open.