Reasons why ReadyThemes often Set Autocomplete = Off

[Bruce - PhosphorMedia]

Like the title says...just curious as to the reasoning behind it...it might make sense in a shared environment...but who shops on shared computers anymore (and why are we still protecting them :) )

[Matt Zimmermann]

Hi Bruce,

Since many of the newer ReadyThemes contain custom JavaScript which is activated on changes to form fields, this setting should help with functionality. Unfortunately, there is no unified style of support across browsers or platforms. I will look into if this is still a viable setting for the future of ReadyThemes.

[Bruce - PhosphorMedia]

Interesting...are you referring to the auto-complete trigger sometimes feeding the DOM onChange event based on browser? Yea, I guess that would be a pain to write based on browser version...i do believe someone wrote a jQuery script that could accommodate this (i.e., I used it once about a year ago and have no recollection where...if I remember, i'll forward it on.)

[lesliekirk]

I may have found another reason not to have autocomplete on - trying to use an address validation service (Addressy). The autocomplete is interfering with Addressy's ability to do its job.

[AHerb]

Had an issue with autocomplete recently => Chrome from time to time is trying to ignore a global autocomplete="off" directive. Because of that customers were not able to register, as some fields in the hidden part of the registration form were autocompleted by chrome.

[lesliekirk]

Had an issue with autocomplete recently => Chrome from time to time is trying to ignore a global autocomplete="off" directive. Because of that customers were not able to register, as some fields in the hidden part of the registration form were autocompleted by chrome.

I used autocomplete="false" and it seems to have worked like a charm.