>>>>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)
>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?
Hard to say. My colleague reproduced the problem in Chrome in his environment. I'll try working with him today, may be we'll get to the root of the problem.
If it's not broken, fix it until it is.
My Blog