Having experiemented a little, I hope you find this useful:
Renaming the fields can cause problems with mass-assignment in Rails, which, although irrelevant as passwords are protected attributes, I don’t like to break in case I want this functionality later.
I have instead added an onsubmit event that blanks the password fields unless you confirmed a new password.
I think the problem is that my email and password are being auto-completed (probably by my browser—not by Tails, right?). So I’ve got my password sitting in the first field of the change password section and an empty password confirm field. When I submit Tails thinks I want to change my password and rightly returns an error when it can’t find the duplicate password to confirm.
Could the first password field use a different name/id to that used on the login page to stop browsers auto-completing it?
Dan Glegg (Project owner)
Having experiemented a little, I hope you find this useful:
Renaming the fields can cause problems with mass-assignment in Rails, which, although irrelevant as passwords are protected attributes, I don’t like to break in case I want this functionality later.
I have instead added an onsubmit event that blanks the password fields unless you confirmed a new password.
Dan Glegg (Project owner)
Yeah, it’s your autocomplete. I’ll have to tweak the field names.
Brook Elgie (Project member)
I think the problem is that my email and password are being auto-completed (probably by my browser—not by Tails, right?). So I’ve got my password sitting in the first field of the change password section and an empty password confirm field. When I submit Tails thinks I want to change my password and rightly returns an error when it can’t find the duplicate password to confirm.
Could the first password field use a different name/id to that used on the login page to stop browsers auto-completing it?