Passwords do not match message

[rick]

Just curious if anyone has/had this same issue.

When I select a user to edit from Access > Users list, the password field is populated with that user's password (confirmation field is blank), and the display is collapsed by default. When I make any change and then attempt to save it, I receive the Passwords Do Not Match message.

When I am logged in as any user, and select Profile from the bottom of the page, the profile data is displayed with the password fields collapsed, but both the password fields are blank, and I do not get the non-matching password warning.

Is there an option to have the password fields initially set to blank?

Currently running 2.16.17 dev on localhost. This issue has been present in previous versions.

Thanks!

[cstevensjr]

When I select a user to edit from Access > Users list, the password field is populated with that user's password (confirmation field is blank), and the display is collapsed by default.

Have you tried overwriting both fields with the password that you require?  What happens if you do that? 

[Mike Rockett]

Both fields are meant to be empty. The password could not be inserted as PW does not know it - after all, it is hashed. You must be using a password manager of some kind, and it may be interfering with the submission process.

[LostKobrakai]

Most likely you're using Firefox. Somehow firefox thinks it's a good thing to prevent developers from disabling auto-fill-in / autocomplete. https://github.com/ryancramerdesign/ProcessWire/issues/1236

[horst]

I have answered to it on Github: https://github.com/ryancramerdesign/ProcessWire/issues/1236#issuecomment-151254248

would this be a solution?

[adamspruijt]

Couldn't this be solved by just using the Ajax field load feature ProcessWire already has, seems that would be an easier solution? I imagine Firefox would not fill a password field loaded this was, though I could be wrong.