There are times that the end-user browser (and password manager) autocomplete facility is a complete disaster.

Two of these are:

  1. The Drupal user edit form, where the browser typically fills in the first password field but leaves the "Confirm Password" field blank. This is no big deal for a sophisticated user, but can drive naive users crazy because of the error they get when they save. And they *know* they didn't want to change their password anyway.
  2. The User Login form, where some security policies really want the user to enter a password, not have one cached from the browser.


This module attempts to help with those two problems by adding "autocomplete=off" to the related forms or form elements. However, browsers and password managers and the like may very well not respect the "autocomplete=off" attribute anyway. For example, Chrome seems no longer to respect it and Lastpass ignores it by default. Read a full rundown on browser support by Chrome, Firefox, and IE. Unfortunately, it seems that browsers have moved away from support, so this module will not have a future.

Please note that this module has nothing to do with the Drupal "autocomplete" function in a form, which can for example help you choose a username or city from a database of options. This module is about trying to control *browser* behavior in autofilling key user forms.

Drush commands

drush na-login
Configures the "autocomplete=off" option on the user login form.
drush na-profile
Configures the "autocomplete=off" option on the user profile edit form.
drush na-summary
Shows the variables status.


As with all contributed modules, when considering submitting an issue:

  1. Read the documentation (two or three times is better). Don't forget the home page.
  2. Review the existing issues list. (Don't forget to select "<- Any ->" for the "Status" field.)
  3. Gather all the appropriate information. This may include (but is not limited to):
    • Drupal version.
    • Browser type and version.
    • Database type and version.
    • Error messages, if any.
    • Module settings.
  4. Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
  5. If you go to provide a patch use the following naming convention:

And please don't forget to use the Issue Summary Template to report an issue, if you need help to understand how the issue queue works, see the Getting Started in the Issue Queue video.

Development version status

The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get by us. Your help on testing this code is greatly appreciated. The translation templates may not always be up-to-date in the dev releases.

Supporting organizations: 
Savas helped port the module to Drupal 7

Project Information