My web application is written using MVC5 and C #.
I have 2 pages where the user can enter their username and password. One of them is the Account Request page, the other is the Login page.
I see different Save Password hint behavior in IE, Chrome and FireFox.
URI:
/Account/RequestAccount /Account/Login
FIREFOX . Allows the user to save a password on any page. When submitting the "Request" form, the user is prompted to save the username / password. If the user wants to save the password, FireFox will autofill when the user returns to the "Login" form. This behavior is desirable and seems correct.
IE and CHROME . None of these browsers suggest saving the username / password when submitting the Account Request form. However, both browsers suggest saving the username / password when the user submits the login form.
Honestly, I don’t see how IE or Chrome can make URI-based distinction, and I don’t believe that they do it. This leaves me suspicious that there might be something wrong with my form fields, except that they work fine on the login page.
Both of my Login and Request accounts use identical form field identifiers (UserName and Password).
<input class="form-control valid" data-val="true" data-val-email="The Username field is not a valid e-mail address." data-val-required="The Username field is required." id="UserName" name="UserName" type="email" value="" aria-required="true" aria-invalid="false"> <input class="form-control" data-val="true" data-val-required="The Password field is required." id="Password" name="Password" type="password">
My question is: is there anything specific that needs to be done in the form fields of the "Account" page to run the "Save Password" request, for example, FireFox? Or IE and Chrome reject the request account page as not the actual login page (somehow)?