Problem/Motivation
While working on the parent issue #3362898: Password input width is incoherent and overflows, we found that password-confirm class is used twice.
Steps to reproduce
1. Go to /admin/people/create page.
2. Search for password-confirm class.
Proposed resolution
Update password confirm class on pass2 password input by password-confirm-field and js-password-confirm to js-password-confirm-field
Remaining tasks
Patch
Review
Commit
User interface changes
NA
API changes
NA
Data model changes
NA
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | interdiff-3-5.txt | 558 bytes | smustgrave |
| #5 | 3374124-5.patch | 10.76 KB | sakthi_dev |
| #3 | interdiff-2_3.txt | 620 bytes | gauravvvv |
| #3 | 3374124-3.patch | 10.06 KB | gauravvvv |
| #2 | 3374124-2.patch | 10.03 KB | gauravvvv |
Comments
Comment #2
gauravvvv commentedI have replaced
password-confirmclass withpassword-confirm-field, Alsojs-password-confirmwithjs-password-confirm-fieldPlease review
Comment #3
gauravvvv commentedFixed the build failure, attached interdiff for same.
Comment #4
smustgrave commentedSeems to be another instance in claro_preprocess_form_element__password_confirm
Comment #5
sakthi_dev commentedPlease review.
Comment #6
gauravvvv commented@sakthi_dev, Please add interdiff with #3.
Comment #7
smustgrave commentedHere's the interdiff missing from #5
Comment #8
lauriiiThis doesn't impact just Claro. We should either add a BC layer for this in Stable, or make the change in Claro theme.
Comment #10
quietone commentedThe Claro theme was approved for removal in #3576460: [policy, no patch] Deprecate and remove Claro.
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3576668: [meta] Tasks to deprecate Claro and the removal work in #3584638: [meta] Tasks to remove the Claro theme.