B
Bogdan
Hi,
I'd like to disable the whole form on the client side right after it is
submitted. There are many controls that could trigger the submit so I'd
like to stay away from disabling each of them individually.
In the past I used to disable individual buttons (with a delay to avoid
'known' problems with events not being raised by disabled buttons). I'd
like to use a similar technique with the form although I'm not sure if this
is necessary. Could someone provide answers to the following questions?
1) If I disable a form on the client side just before it gets submitted will
the asp.net handle it the same way as if it were enabled?
2) What is the best place to plug-in my form disable script? For example,
how should I register the following script in an aspx page?
function disableForm() {
document.getElementById("aspnetForm").disabled = true;
}
Thanks,
Bogdan
I'd like to disable the whole form on the client side right after it is
submitted. There are many controls that could trigger the submit so I'd
like to stay away from disabling each of them individually.
In the past I used to disable individual buttons (with a delay to avoid
'known' problems with events not being raised by disabled buttons). I'd
like to use a similar technique with the form although I'm not sure if this
is necessary. Could someone provide answers to the following questions?
1) If I disable a form on the client side just before it gets submitted will
the asp.net handle it the same way as if it were enabled?
2) What is the best place to plug-in my form disable script? For example,
how should I register the following script in an aspx page?
function disableForm() {
document.getElementById("aspnetForm").disabled = true;
}
Thanks,
Bogdan