Password field autocomplete=off is ignored in several browsersDescription The autocomplete="off" is being ignored by the following browsers, causing the Password field in the sys_user form to be autofilled with the user's name and password for some users.- Internet Explorer 11- Firefox v38.0.1- Google Chrome v45+The issue is occurring when the password is saved for the specific instance in the browser. IE11 and Firefox v38 browser are autofilling any Password fields in the instance with this saved information if the field before the password field is empty. If the field before the Password field is not empty the issue is not reproducible. The issue is not reproducible in Firefox v37. The issue is also reproducible in Chrome in the latest release.The following questions were posted in Firefox Support:- https://support.mozilla.org/bs/questions/1064817- https://support.mozilla.org/en-US/questions/1063227 This is a new behavior introduced with Firefox itself. The ability for websites to disable the password manager using autocomplete = "off" is being removed in Firefox 38. The behavior difference is also listed in the release notes.:https://www.mozilla.org/en-US/firefox/38.0/releasenotes/ Steps to Reproduce Ensure that you have the password management capability enabled in the browser.Login using Firefox v38 or IE11 browser.During login, reply yes to the password manager message. For example, in Firefox, the message says "Would you like to remember the password for XXXXX on service-now.com?"To ensure that the password is saved, logout and check if your user name and password are automatically populated.\After login, navigate to sys_user list.Select a user with empty Department field.Assuming that the base system form layout is not changed and the Department field is the field before the Password field.Open the record. For example, soap.guest.The user name appears in the Department and the Password field is filled in with dots. This is due to the Password manager at the client side. Workaround There is no known workaround for this issue. If you are able to upgrade, review the Fixed In field below to determine the versions that have a permanent fix. You can also subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue. Related Problem: PRB632426