As a matter of security, no browser will EVER "echo" the password back after a postback. This is by design, and you should carefuly consider why this would be a requirement. Almost everybody knows that registration form errors (processed after a postback) as well as login forms, etc., clear the password, so I suggest you're better off educating users instead of bypassing this feature. Let them save their passwords in the browser if they want to, but remember its THEIR responsibility if they do so.
Dig Deeper on .NET Framework security best practices
Related Q&A from Daniel Cazzulino
Here Daniel Cazzulino explains how to load a DSL (domain specific language) domain model instance file programmatically. This requires the .NET type ...continue reading
Here we offer a glimpse at 12 of .NET development expert Danny Cazzulino's top ASP.NET questions and answers.continue reading
C# developers should NOT be modifying InitializeComponent method in the code-behind (or any of the variable definitions) by hand.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.