5 ms·
Is it me, or why is a setTimeout needed in this example? $(document).ready(function(){ $("form").submit(function(){ setTimeout(function() {
by nodesocket 12y ago
Is it me, or why is a setTimeout needed in this example?
$(document).ready(function(){
$("form").submit(function(){
setTimeout(function() {
$('input').attr('disabled', 'disabled');
$('a').attr('disabled', 'disabled');
}, 50);
})
});
- kacperp 12y agoWas asking myself the same thing. This would make sense if your submit button will actually cause an ajax request that you might want to repeat. But actually submitting the form will cause a page reload either way, or not?
- seszett 12y agoSome browsers will not submit the form if you disable the submit input inside the submit event.
- nailer 12y ago50 should be a constant called NEXT_TICK with a value of 0. This makes it run on the next event loop, ie, default event submit form, next tick afterwards the form is disabled
- xrstf 12y agoYou are looking for setImmediate[1]. EDIT: Oh, never knew that this method was a Node-ism only. [1] https://developer.mozilla.org/en-US/docs/Web/API/Window/setImmediate https://developer.mozilla.org/en-US/docs/Web/API/Window/setI...
- nailer 12y agoActually it's common enough that var setNextTick = function(nextTickFunction){window.setTimeout(nextTickFunction), 0}) ...sounds like a damn good idea. Hate the name 'setImmediate' though, immediate implies the current tick and people would wonder why you're using it.