Closed (fixed)
Project:
Drupal core
Version:
10.1.x-dev
Component:
Claro theme
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 May 2023 at 08:52 UTC
Updated:
26 Jul 2023 at 13:39 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
kopeboySaid CSS is actually in Claro (I haven't tested with other themes).
Comment #3
kopeboyComment #4
lauriiiThanks for the bug report @kopeboy! 😊
The
.password-confirmselector is supposed to target the wrapper of the passwords but it looks like the class is also applied on the second password item. 🙈 I think the right fix here would be to remove thepassword-confirmclass from thepass2password input.Comment #5
Vidushi Mehta commentedAdded a patch which is targeting the password strength as mentioned by the @kopeboy, I've checked on Olivero theme, same issue is showing there as well. Added before & after screenshots of the claro theme and one screenshot for the Olivero.
@lauriii are we removing the class as it should not be repeated on the child selector? Or any other specific reason for that please confirm
Comment #6
smustgrave commentedIS needs to be updated with proposed solution in #4
Comment #7
athyamvidyasagar commentedThe password field is in consistence compare to other fields. Now with this patch all the fields are rendering in 100%. Screenshot is attached.
Comment #8
gauravvvv commentedI have added a patch with different approach. In patch #5, we are limiting the password strength with 25ch.
On the parent we already have max-width of 25rem; If we give input fields, width: 100% then it is aligning with the password policy as well. I have attached a patch and after patch screenshot for reference. Please review
After Patch
Comment #9
gauravvvv commentedIgnore patch #8, I have made all changes into #9.
Comment #10
smustgrave commentedSeems issue summary still needs to be updated please.
Comment #11
gauravvvv commentedComment #12
smustgrave commentedThanks
Comment #15
lauriiiThe fix in #9 looks good and I confirmed it addresses the original issue. We could fix the issue related
.password-confirmapplying to multiple elements in another issue.Committed 4d30ef7 and pushed to 11.x. Also cherry-picked to 10.1.x as this is a low risk bug fix to Claro. Thanks!
Comment #16
gauravvvv commentedOpened a follow up issue for .password-confirm #3374124: Remove the password-confirm class from the pass2 password input