Current behaviour:
Now every browser comes with save password option.
If the password is saved by a browser when we reload a page that contains form password field. By default, it is set to invalid even though the browser fills password field. On clicking anywhere on the page it is set to valid.
Here is the plunker demo.
This is a plunker. I forked from the internet for the demo.
How to recreate the issue

here after reload, the password field changed to true after the click.
This behaviour is only with input type="password".
Expected / new behaviour:
If a valid password is auto-filled by browser then it should be made valid
Can you please post a reproduction? It sounds very similar to https://github.com/angular/angular.js/issues/1460 which should have been fixed by all major browsers.
I tried reproducing that in plunker. but chrome doesn't autofill username or password field in plunker while page load. I am not sure why that happens.
The issue I created happens only when browser autofill password on page load.
I will try reproduce in some other ways
I think that's because plnkr is run in an iframe. There's a "external run"
option with which it should work
Am 18.05.2017 20:40 schrieb "Sibiraj" notifications@github.com:
I tried reproducing that in plunker. but chrome doesn't autofill username
or password field in plunker while page load. I am not sure why that
happens. I will reproduce in some other ways—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/15985#issuecomment-302504956,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGYSfQtM-Y_lZdp4fLzIwdgen3U5agYks5r7JB7gaJpZM4NaYvP
.
@Narretz . Here is the plunker demo.
This is a plunker. I forked from the internet for the demo.
How to recreate the issue
Sorry for the delay.
@Narretz . also I updated my PR too.
@Sibiraj-S Do note that the plunkr you've linked is using AngularJS 1.2.x, which is a very old version of AngularJS.
Could you check if the issue exists with the latest version of AngularJS (1.6.4) ?
Also note that you have to use the same version for all angularjs modules...
<script src="//code.angularjs.org/1.2.20/angular.js"></script>
<script src="//code.angularjs.org/1.2.20/angular-route.js"></script>
<script src="//code.angularjs.org/1.2.13/angular-cookies.js"></script>
The above versions are not supported to work together.
My bad @frederikprijck . check this one https://plnkr.co/edit/jWpHLhrLjWSRIYoYnLnM?p=preview.
I forgot to change version. but both have same problem I guess
I double checked with the latest version 1.6.4 too.
@frederikprijck . is this issue has enough info now?
@Sibiraj-S Alright, for me it doesn't work with AngularJS 1.6.4 either.
@Narretz It looks like I'm also having the exact same issue when running the above plunkr. It works fine for the input text, but not for the password.
I cannot reproduce this in Version 59.0.3071.109 (64-Bit)
After I've been logged out, Chrome correctly fills user and password field, and I can simply click on login and it works.
everything happens fine. The chrome fills passwords correctly.
but,
Check the plunker.
Reload the page after logout. the password field is set to invalid until any click happens
Oh, I see it now. This looks like a Chrome bug / wuirk, but we should investigate why it only doesn't work with password fields.
This happens because autofilling the password field does not emit an input event (which would hint AngularJS that the field's value may have changed). This does indeed sound like a browser bug (but could be intended behavior - I can't be 100% sure).
In any case, I am going to close this, because there is nothing we can do for this on the AngularJS side. (If anyone has ideas, I would be happy to discuss.)