IE does not offer to save ASP.NET form password

Question

Sometimes Microsoft does something so stunningly dumb that my head hurts. Help me find out that this is really not the case ... please!

I have a problem with the login page to the ASP.NET site (3.5) that I am developing, as a result of which IE (7 or 8 ... cannot open 6) does not offer to save the password when the user logs in. I checked other browsers, and Firefox, Chrome and Safari offer to save the password just fine. I also confirmed that saving IE password in my test windows works fine on other sites and, for example, Google, etc. It works great.

The search I did has changed very little, but it seems that little has shown that IE will not offer to save the password if the form on the page contains more than two text controls. This is the case with my form, which also has controls that allow the user to register. And when I remove these additional controls, IE magically suggests saving the password, so it looks like the truth.

Now ... if ASP.NET allows me to have several forms, everything will be fine, and I will be able to highlight two functions in stand-alone forms, and IE will offer to save passwords. But ASP.NET does not allow me to do this, since it allows only one form. I could lure here not runat = server and try to do it, but guess what? Since my page uses MasterPage, any form tag that I add is automatically deleted, even if it is not runat = server form.

So, I see no way to get around this without fundamentally changing what I was trying to achieve. It seems like I should explain to my users that they will not be asked to save their passwords if they use IE (Microsoft product), because I developed my site using ASP.NET (error ... Microsoft product).

If so, I just can't figure out how funny this is. If anyone can suggest any ideas on how to get around this, tell me that everything turned out wrong and I am also a big stupid idiot, or just want to confirm that it is not only me who considers it monumental stupid then please do please.

Just for the record, I really don’t want (and I don’t understand why I need it) to compromise my design and divide my pages into two parts (which will lead to a worse experience for the user).

Answer 1

@Chris That's what I went to the end.

So, for someone else, I still have activation controls in the form of runat = server and process them in the code for this page. Then I have a second standard HTML form with HTML input text fields that are sent to another .NET page. This applies to user login. I take the values ​​on this page through Request.Form and process the login here.

Simplification:

Everything works, and users remember their logins as they expected.

Downsides:

I lost the ability to use MasterPage (since I need two forms on the page), so I really had to duplicate the template - I don't like it.

If the user's login is invalid or causes some kind of error, I must redirect to the start page and pass the flag to it so that it displays the corresponding error message. I don't like that either.

As I said, it just works, and in this case it is the most important. Thanks for your input.