I have a login form for a user to type his/her password. This form is bound to an AngularJS model. Suppose that in the corresponding controller the user-given password is av
If this is a real risk for your app, your only real choice is to create a page for login that is separate from the application.
You can use a standard login form to submit the password, the response will force the browser to fetch a new page, and all existing memory with a password is ignored.