I saw this on our website when the user clicked an AjaxLink that ran long and
then clicked another AjaxLink before the response was received. We added a
DIV overlay to the ajax spinner and implemented IAjaxIndicatorAware on our
page so that all AjaxRequests would have the overlay with a
I think the conclusion from the wicket reaction game was (which
consisted of a grid with a lot clickable fields and had this issue a
lot), either to veil. Or wait and see if there's anything in Wicket
1.5 that prevents this.
Im not sure if theres some thing you can override that would let
Wicket
http://www.lmgtfy.com/?q=wicket+veil
Best Regards,
Ilja Pavkovic
Am Samstag, 9. Januar 2010 22:32:06 schrieb Douglas Ferguson:
Anybody have any thoughts on how to systematically deal with this problem
rather than updating every link to disable after onclick..
D/
On Jan 8, 2010,
Hmm.. Would this really be resulting from the site being slow? Or the client
being slow?
D/
On Jan 8, 2010, at 12:46 PM, nino martinez wael wrote:
I your site is slow and the user manages to click the delete twice i
could happen (I can see you write that too)..
Put a veil over the button
Anybody have any thoughts on how to systematically deal with this problem
rather than updating every link to disable after onclick..
D/
On Jan 8, 2010, at 12:46 PM, nino martinez wael wrote:
I your site is slow and the user manages to click the delete twice i
could happen (I can see you
Our application periodically gets these errors, where wicket say the component
could not be found.
Take this example.
1) There is a delete link on the page.
2) The user clicks the delete button
3) They get the delete button component not found error.
The intriguing part is that the item is
I your site is slow and the user manages to click the delete twice i
could happen (I can see you write that too)..
Put a veil over the button when it's clicked so the user cant click it twice..
2010/1/8 Douglas Ferguson doug...@douglasferguson.us:
Our application periodically gets these errors,
