On Wed, Oct 15, 2008 at 12:31 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote: > We had a "double submit" bug that allowed a form to be submitted twice when we > weren't fully prepared for that. We are still researching the best practices > to > address this a general case. One approach we are considering is change the > submit action on forms with JavaScript, so it disables the submit button, and > then actually submit the form, preventing one kind of double-submission. It > seems like I don't see this approach happening in the wild much, though. I > suspect there is a better solution.
JavaScript is okay, but can be a problem when people hit back expecting to use the form again and the button is still disabled. Another approach is a unique ID in the form that you track in the user's session (i.e. this ID was seen before). If the problem is large uploads with no feedback until they finish, you can use one of the upload progress tools. - Perrin
