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

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pguillard’s picture

pguillard’s picture

Status: Active » Needs review
Manjit.Singh’s picture

Assigned: Unassigned » Manjit.Singh
Manjit.Singh’s picture

Issue summary: View changes
Manjit.Singh’s picture

Assigned: Manjit.Singh » Unassigned
Status: Needs review » Reviewed & tested by the community
FileSize
110.23 KB
81.9 KB
117.98 KB
112 KB

I have tested the error and their respective classes. Please check the screenshots of error messages.

alt

alt

alt

alt

xjm’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for the manual testing!

I checked to confirm that this replaces all instances of these classes:

[mandelbrot:maintainer | Sat 14:18:05] $ grep -r "form\-error\-message" *
[mandelbrot:maintainer | Sat 14:18:11] $ grep -r "form\-error" *
[mandelbrot:maintainer | Sat 14:18:16] $ 

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!

  • xjm committed 134aba9 on 8.0.x
    Issue #2501903 by pguillard, Manjit.Singh: inline form errors classnames...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.