Yes, as I said, it's not for me, it's for users of my sites; those updating their own profile who are getting confused.
And a lot of people have password extensions now. They don't necessarily understand how to control them but they have them because they are worried about security.
It's browser or browser extension behavior. So there's not much that can be done about it. Standard browser auto complete (no extension) should respect the attribute (they don't have to though), but extensions don't have to (e.g. LastPass doesn't care about the attribute). The attribute didn't become standard until HTML5 so until then browsers didn't even need to treat it as if it existed.
1. If I were to put the password into it's own Tab would it still autofill when users are updating?
Yes, the browser doesn't care where it's at. It finds it in the DOM and changes the value.
2. Could I change the name of the Password field without disrupting the code?
No, that's a core field and you can't change the name without causing a chain of bugs. It wouldn't matter anyway as the browser would learn the new input name and then you're full circle with the same issue. A lot of browser extensions don't even care what the name is and are purely looking for password type.
Maybe if the field was named "Your Password" the autofill would leave it alone?
No.
Probably the only solution is some sort of weird JS solution that trys to empty the field after the page is done loading. Whether that works or not I've no idea though as browser behavior typically kicks in after the page has loaded so it may not do anything at all.
krileon
