We have found a fundemental problem with the way that
postbacks are handled. We have a page that has about 60
postback controls that are posted back to the server when
the user clicks a link (LinkButton).
The page takes about 5 seconds to render. A problem occurs
when the user clicks the link, gets the page back to the
browser, then immediately clicks the postback link again.
In this situation the page has not finished rendering, but
gets interuppted and posts back the data to the server.
We find that only some of the postback items in the form
are being returned to the server. Instead of 60 items
coming back, we now have received only (say) 30 items.
The consequence of this, is that the postback controls
whose values were not passed back are now considered to be
blank. When the page renders again, the values of those
controls have been lost!
Someone must have come across this problem before?
How do we stop the user from pressing the postback button
before the page has finished rendering?
We thought of trapping the onSubmit of the form (in
JavaScript), but this only fires for real Submit buttons,
our postback control is a LinkButton. Alternatively, is
there a way to alter the standard __doPostBack function?
Or is there another solution?
