>>>Hi everybody,
>>>
>>>When I am testing a form from the local development environment, I am always getting ng-dirty for operator code and password input fields. These fields are not even visible (class ng-hide) in the edit mode, so that ng-dirty flag along with ng-untouched makes very little sense.
>>>
>>>Also, this problem only shows up in Google Chrome, IE and MS Edge browsers do not show these two controls with ng-dirty.
>>>
>>>When I test that exact page in QA site (with the latest code from development), that page is correct and both controls show ng-pristine.
>>>
>>>How can I figure out why my development environment is so deceiving and why that problem only shows up in Google Chrome?
>>>
>>>Thanks in advance.
>>
>>Don't really know but a couple of points:
>>
>>ng-hide basically sets 'display: none (so the element is still in the DOM)
>>
>>The environment should not really make any difference - localhost, whatever - it's all happening in the browser, So if you are getting different results then there's a difference in code.....
>
>The code seems to be exactly the same. When we're sending our changes to TFS, the automated build sends the code to the QA server as well. But, in QA server it works correctly for me and when I run it locally from VS (F5 or Ctrl+F5 - doesn't matter) I get the wrong behavior in Chrome.
>
>That's why it's strange. Of course, the database data is also different, but that should not make any difference, I think.
>
>If you want, I can send you the link in PM to test (although I don't know if you'll be able to access it).
>
>BTW, I can see that the code is my latest as I was the last person working on that form and I removed placeholder thinking it may help. The QA server doesn't have placeholder in these 2 inputs.

Send a link if you like - but I'm not sure I'll get time to try it.
Is it possible that either Chrome or localhost is caching that page?