Yes, i have it some times : it can happen if you have a SMTP password OR a IMPA password.

BUT : form seems clean .....

Not in 2.50 no autocomplete="off" is set

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=18949

Not really resolved ... new browser don't activate "autocomplete".

See http://stackoverflow.com/a/21348793/2239406 and http://caniuse.com/#feat=input-autocomplete-onoff (end of page : partial only on all browser)

I try adding 2 false input

• for smtp user : seems to work (FF42)
• but for imap user : don't work (FF42)
  (see http://stackoverflow.com/a/23234498/2239406)

Maybe leave it with "not fixable" => browser behaviour
See another source : https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion#The_autocomplete_attribute_and_login_fields

http://caniuse.com/#search=autocomplete

Good enough for me.

Maybe enough , but don't wrok:

<quote>
This support information does not include support for other autocomplete values.

As described in detail below, many modern browsers ignore the off value on certain fields in certain cases intentionally in order to give the user more control over autofilling fields. One example is the use of password managers.

1 Partial support refers to ignoring the off value for password fields. see related blog post

2 Partial support in Chrome refers to the browser intentionally ignoring autocomplete="off" when the user uses the browser's autofill functionality. see bug

3 Partial support in Firefox refers to ignoring autocomplete="off" for login forms. see bug

4 Browser does not display previously submitted values as options with on value.

5 Safari ignores the off value for username, email and password fields
</quote>

Yes, I can read.

Yes, but then "Not fix" or something other, but not "fixed" no ?

Version 2.50 Build 160512 released