Rey, As has been suggested, you can dynamically name form fields, or try autocomplete="off", but after all is said and done, the client ultimately has control over caching that autocomplete data. Even if you change the form field name, the autocomplete data's being sotred on the client, it's just stored using a different form field name every time. Some might argue that this actually would create a BIGGER security risk for your users since you re essentially forcing them to store the credit card info over and over with different form fields each time.
Either way, the browser makes the ultimate decision as to storing the form field data, how long to keep it, where to keep it, and how secure it is on the end user's computer. You can only do so much to protect your users from storing data insecurely on their own machines. You may serve your users better by just turning autocomplete="off" and adding a quick link or hint informing (educating) the user that they should be not turn autocomplete on for data the deem "secure" or private. Of course that opens up a whole new ball of wax if you start trying to educate your users... -Cameron -- Cameron Childress Sumo Consulting Inc http://www.sumoc.com --- cell: 678.637.5072 aim: cameroncf email: [EMAIL PROTECTED] On 1/9/06, Rey Bango <[EMAIL PROTECTED]> wrote: > Guys, > > Is there a way to prevent a browser's autocomplete/autofill feature from > caching info on certain forms? For example, I don't want a credit card > form field to be cached via autocomplete. The same with login prompts. > > Anyone tackled this before? > > Rey... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228981 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
