Problem/Motivation

You will notice that when viewing the register form you will see "Passwords Match:" showing below the second confirm password box. It should be hidden initially when the page loads and only show as you start to type the second password. When you start typing your password the text will disappear.

This was introduced with: #1751434: Selectors clean-up: user module
This changed the class on that wrapper field from .password-confirm-match to .password-confirm, the CSS that controls this element was not updated and still has the old id (https://github.com/drupal/drupal/blob/8.4.x/core/modules/user/css/user.m...).

This could be fixed by the (long) upcoming #2293803: Replace confirm password element with a new password element with show/hide functionality but is a bug that needs fixing till then.

Steps to reproduce

Drupal 10.1.x, this occurs with Stark and Olivero but not Claro.

Proposed resolution

TBA

Remaining tasks

Decide if the password strength text should be in included in this change.
Update patch
review
commit

User interface changes

API changes

Data model changes

Release notes snippet

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rbrandon created an issue. See original summary.

rbrandon’s picture

Status: Needs work » Needs review
FileSize
1.05 KB

This patch changes the class back to password-confirm-match this both distinguishes it from the input with the same class, and fixes the css hide issue.

rbrandon’s picture

For a patch for this issue along with #2862278 see https://www.drupal.org/node/2862278#comment-12002956.

LoMo’s picture

Status: Needs review » Needs work

I'd hoped to be able to move this issue along, since it's been sitting with no action for so long, but I still see the "Passwords match:" text when the page loads, even after applying the patch. (And yes, even after clearing both Drupal and browser caches.) Maybe something has changed since your patch was created. Or maybe I'm missing something, but at least I've attempted to test your patch and don't see any visible difference there. I've tried with both the /admin/people/create user-form and with a plain authenticated user logged in (editing own password on "user/123/edit"). In all cases the behavior is as you describe and applying the patch does not seem to change it.

jludwig’s picture

Note: the issue summary mentions that "This could be fixed by the (long) upcoming https://www.drupal.org/node/2293803 but is a bug that needs fixing till then," but that issue adds the new show password functionality as a configuration that is off by default, so this will be needed even if that issue does get in.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

toddses’s picture

Quick patch that includes a CSS class change that resolved the issue for me. Seems at this point, the CSS just needs to be updated to the new class.

toddses’s picture

patch in #13 doesn't apply cleanly, rerolling.

anmolgoyal74’s picture

Status: Needs work » Needs review
FileSize
362 bytes

Added patch for 9.2.x

Status: Needs review » Needs work

The last submitted patch, 15: 2862256-15.patch, failed testing. View results

nikitagupta’s picture

Status: Needs work » Needs review
FileSize
358 bytes
sulfikar_s’s picture

Status: Needs review » Needs work
FileSize
7.38 KB

Hi, the patch in #17 applied cleanly. But doesn't make any change. The "Passwords Match:" text still shows on page loading.

I'm attaching the screenshots below,

after-patch.png

I think this needs work!

anmolgoyal74’s picture

Status: Needs work » Needs review
FileSize
4.42 KB
3.7 KB

Updated tests.

Status: Needs review » Needs work

The last submitted patch, 19: 2862256-19.patch, failed testing. View results

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Issue summary: View changes
Issue tags: +Bug Smash Initiative, +Needs issue rescope

This was a bugsmash daily target, discussed by myself and lendude.

The issue is still valid. On Drupal 10.1.x, it occurs with Stark and Olivero but not Claro. It is not clear why this is only changing the 'match' text and not the 'strength' text as well. Tagging for an issue rescope to consider that question.

Prem Suthar’s picture

Re-roll the Patch For 10.1 Branch.

ameymudras’s picture

Status: Needs work » Needs review

Moving the issue to NR as the patch is submitted in #26

Status: Needs review » Needs work

The last submitted patch, 26: 2862256-26.patch, failed testing. View results

Indrapatil’s picture

Assigned: Unassigned » Indrapatil
Indrapatil’s picture

Assigned: Indrapatil » Unassigned
Meeni_Dhobale’s picture

I tried the last updated #26, and it seem that issue is not soved yet. Need to work on this.

ranjith_kumar_k_u’s picture

Updated the tests as per the provided solution, and not changing the status to Needs Review because of the Needs issue rescope

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.