I want to prevent multiple form submissions using angular.js. The question is related to this question.
When the user clicks on a form submit button the value / label of the submit button should change to "loading..", status of the button will be set to disabled AND the submit event should be triggered in the normal way, leading to a submit call to the server. This way the user would see the following effect:
Immediately: The submit button value changes to "loading.." and gets disabled
As soon as the server responds: user gets presented the result of the server request (whereas server responds are handled without angular intervention)
I created this plunk to show what I mean. My issue relates to this line: elm.attr('disabled',true);
. This does not only disable the button, but also prevent to propagate the submit event. Thus I get a disabled button (desired result), but the form does not get submitted (undesired result).
You can see the changing behavior if you comment / uncomment this line : elm.attr('disabled',true);
Any idea how to change this?
I ended up going the directive route as well. The following is used instead of ng-click and expects the passed in function to return a promise (which restangular does). When the promise is resolved (response is returned) - it will allow subsequent submittals. Could also tweak this to add/remove ng-disabled.
The easiest and most common way of doing it is to rely on
$submitted
property of form object like so:Alternative (flexible & simple) solution (inspiration) : a wrapper function around the submit code that sets a scope variable. See live example.
Usage in controller:
in view:
The function (put it in a service):
Try a $timeout (the angularjs function)
An addition to spenthil answer, a variant in coffee script + you can enable a button back if you need (e.g. when a form validation has failed and you want to try again)
here is the simple way to do similar stuff with simple logical checks, text change can also be done in similar fashion.