Hidden form fields also saved about jquery-save-as-you-type HOT 4 CLOSED

Hey there, if you look at the readme there are already ways to exclude certain fields from being saved.

from jquery-save-as-you-type.

Sure, and I did that, but it was too late for those users who had already visited the site and the plugin had saved the data in the hidden form fields. Once we, as the form's creators, changed the data in those hidden form fields, there's no way really - short of asking the end user to hit a button to clear the data - to clear that out and I don't think the end user should be responsible for that anyway.

Let me give you a practical example. This form is sending payment data to a payment gateway and the hidden form fields hold things like account id, form id, etc. Those are things that don't really need to be saved since they are more or less hard-coded into the field, until such a time that we want to change them.

All I'm suggesting is that hidden fields should be excluded by default since I can't really see any application that would require hidden form fields to need to be saved, and it is, again, IMHO unexpected behavior.

Thanks.

On Sep 30, 2014, at 11:55 PM, Ben [email protected] wrote:

Hey there, if you look at the readme there are already ways to exclude certain fields from being saved.

—
Reply to this email directly or view it on GitHub.

from jquery-save-as-you-type.

I understand what you mean, but I think in reality thats counter intuitive. This plugin was designed designed to be an include all except specified fields - add all except these - and changing that behaviour would mean completely changing it's original concept.

Many people like to hold things in hidden fields that are important to the form but not for presentation - and want to keep that in the event that the cookie data is recovered. This could be something as simple as a timestamp - we can't just exclude one type of field by default when all others aren't.

Additionally, I'd not suggest using this on a payment form, even for just things like account ID's - that kind of data should be handled entirely by the session.

I'll update the docs to explain that hidden fields are automatically included and should be explicitly excluded if you don't want that data saved so that no one else falls foul of the same type of expectation.

from jquery-save-as-you-type.

I understand. I did figure that just because I couldn't think of an application, there was probably someone out there who would need it.

Thanks for your explanation and thanks again for this plugin.

On Oct 1, 2014, at 1:29 PM, Ben [email protected] wrote:

I understand what you mean, but I think in reality thats counter intuitive. This plugin was designed designed to be an include all except specified fields - add all except these - and changing that behaviour would mean completely changing it's original concept.

Many people like to hold things in hidden fields that are important to the form but not for presentation - and want to keep that in the event that the cookie data is recovered. This could be something as simple as a timestamp - we can't just exclude one type of field by default when all others aren't.

Additionally, I'd not suggest using this on a payment form, even for just things like account ID's - that kind of data should be handled entirely by the session.

I'll update the docs to explain that hidden fields are automatically included and should be explicitly excluded if you don't want that data saved so that no one else falls foul of the same type of expectation.

—
Reply to this email directly or view it on GitHub.

from jquery-save-as-you-type.