prevent a click happy user???


So a product I have been working on is in SQA and they have uncovered what is considered a defect in my implementation. I should point out that navigation is link based via a drop down CSS menu.

Essentially the tester clicks a ton of links after issuing a post to the server. The browser queues up all the requests but the result is the browser slows down in behavior until the code catches up (if that makes any sense).

Do folks prevent additional requests while one is pending? Seems like a dangerous proposition in a stateless system where the initial request might not return?

The short answer is to not click like that I know... :slight_smile:

However, I am looking for any insight.

thanks, Rick