Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
When #1493324: Inline form errors for accessibility and UX is commited we must fix the classnames so it fits with the coding standards.
Proposed resolution
form-error-message
to field-item--error-message
and form-error
to form-item--error
etc
Remaining tasks
get #1493324: Inline form errors for accessibility and UX into core ;)
User interface changes
none
API changes
css classes
Comment | File | Size | Author |
---|---|---|---|
#5 | after-3.png | 112 KB | Manjit.Singh |
#5 | after-2.png | 117.98 KB | Manjit.Singh |
#5 | after-1.png | 81.9 KB | Manjit.Singh |
#5 | after.png | 110.23 KB | Manjit.Singh |
#1 | inline_form_errors_classnames_namestandard-2501903-1.patch | 5.21 KB | pguillard |
Comments
Comment #1
pguillard CreditAttribution: pguillard commentedit's a start ..
Comment #2
pguillard CreditAttribution: pguillard commentedComment #3
Manjit.SinghComment #4
Manjit.SinghComment #5
Manjit.SinghI have tested the error and their respective classes. Please check the screenshots of error messages.
Comment #6
xjmThanks for the manual testing!
I checked to confirm that this replaces all instances of these classes:
This issue only changes user-facing strings, CSS, or markup, so per https://www.drupal.org/core/beta-changes, this can be completed any time during the Drupal 8 beta phase. Committed and pushed to 8.0.x. Thanks!