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

Comments

Gauravvvv created an issue. See original summary.

gauravvvv’s picture

Status: Active » Needs review
StatusFileSize
new10.03 KB

I have replaced password-confirm class with password-confirm-field, Also js-password-confirm with js-password-confirm-field

Please review

gauravvvv’s picture

StatusFileSize
new10.06 KB
new620 bytes

Fixed the build failure, attached interdiff for same.

smustgrave’s picture

Status: Needs review » Needs work

Seems to be another instance in claro_preprocess_form_element__password_confirm

sakthi_dev’s picture

Status: Needs work » Needs review
StatusFileSize
new10.76 KB

Please review.

gauravvvv’s picture

@sakthi_dev, Please add interdiff with #3.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new558 bytes

Here's the interdiff missing from #5

lauriii’s picture

Status: Reviewed & tested by the community » Needs work
--- a/core/lib/Drupal/Core/Render/Element/PasswordConfirm.php
+++ b/core/lib/Drupal/Core/Render/Element/PasswordConfirm.php

@@ -85,7 +85,7 @@ public static function processPasswordConfirm(&$element, FormStateInterface $for
-        'class' => ['password-confirm', 'js-password-confirm'],
+        'class' => ['password-confirm-field', 'js-password-confirm-field'],

This doesn't impact just Claro. We should either add a BC layer for this in Stable, or make the change in Claro theme.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.