Use JavaScript to prevent double submission of admin forms

[Manuel Saelices]

For fast clickers.

[Manuel Saelices]

Fixed on this Pull Request: ​https://github.com/django/django/pull/9425

[Aymeric Augustin]

I think this is an improvement and the implementation looks reasonable.

[Tim Graham]

I found an article titled ​JavaScript: Preventing Double Form Submission which might be worth reviewing. In particular, it points out "Rather than simply disabling the button, we can also change the text so that people don't get confused."

Did you consider trying to add some tests for the patch?

I share Nick's concern on the pull request that this may have a good chance of causing some regression in unconsidered edge cases. I'm not sure if it's considered a best practice these days. The article suggests that some browsers (e.g. IE11) treat a double click as a single click. It seems unfortunate if every project has to add something like this.

[Karan Bedi]

I have created a PR. Please guide me how to proceeding further.
​PR

[Carlton Gibson]

Hi Karan,

Thanks for the input. Your fix includes the changes Nick suggested from the original PR. (Great.)

To get this merged we need to address Tim's concerns.

• Can we add some selenium tests, to exercise the behaviour?
• What's your assessment of the article Tim linked to? Do we need to do this?

[Karan Bedi]

Hi Carlton,

• I am unable to reproduce the behavior, probably because till now, I am serving on localhost.
• In the article, there are different methods of implementing the same. One improvement can be changing the label of the submit button after a click.
• From the point of usability, there is just a comment by someone, which also doesn't seem concrete.

Please guide me on how to proceed further.

[Marcelo Galigniana]

For this issue there are currently 2 approaches:

• ​Trigger an alert when submitting twice

• ​Disable buttons while submitting

[Marcelo Galigniana]

I think thibaudcolas's comment in 1st approach makes sense: ​https://github.com/django/django/pull/15217#issuecomment-1018935149

So I updated the PR to go for the first option

[Carlton Gibson <carlton@…>]

In fe7dbef:

Fixed #28889 -- Prevented double submission of admin forms.

Added a JavaScript confirm() to catch double-submissions, when the
change form has already been submitted.

Thanks to Adam Johnson, Claude Paroz, Keryn Knight, and Thibaud Colas
for review.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 0756c61f:

Fixed #33893 -- Reverted "Fixed #28889 -- Prevented double submission of admin forms."

Regression in fe7dbef5867c577995f0fc849d8dfdb8f2e6bbfa.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 82e9e19:

[4.1.x] Fixed #33893 -- Reverted "Fixed #28889 -- Prevented double submission of admin forms."

Regression in fe7dbef5867c577995f0fc849d8dfdb8f2e6bbfa.

Backport of 0756c61f2ada56e4ae625589099c0141a77737eb from main

[Mariusz Felisiak]

Patch was reverted, it's probably not worth complexity.

[Ömer Faruk Abacı]

In our production environment, we encountered this issue with inlines. Adding an inline object and mistakenly clicking “Save” multiple times resulted in multiple requests, leading to the insertion of the same inline object multiple times. To resolve this, I disabled the buttons on form submission by overriding admin/submit_line.html as follows:

{% extends "admin/submit_line.html" %}
{% block submit-row %}
    <script>
        django.jQuery(document).ready(function() {
            django.jQuery('form').on('submit', function(event) {
                django.jQuery('input[type="submit"], button').prop('disabled', true);
            });
        });
    </script>
    {{ block.super }}
{% endblock %}

I understand the concerns raised in previous discussions about network failures potentially leaving buttons disabled and preventing further user actions. However, I believe we need to weigh which scenario is worse: adding duplicate entries or requiring users to re-enter their changes. Additionally, we should consider which is more likely: mistakenly clicking “Save” twice or experiencing a network failure. IMHO, it might be good to address this issue to enhance the user experience and data integrity.