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 fail in silence (which essentially are what you are looking for) when encountering missing components during ajax. regards Nino 2010/1/9 Douglas Ferguson <[email protected]>: > 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 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 <[email protected]>: >>> 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 actually deleted. >>> >>> This makes me think it could be a double click error. >>> i.e. the item is delete and the js has another click call queued up but the >>> page changes before it comes through. >>> >>> Is this possible? If so how do I prevent it? >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
