Re: How to prevent user from double-clicking a non-Ajax component

[Martijn Dashorst <ma...@gmail.com>]

This is in the category how do we prevent the user from doing stupid
things... like not clicking the log off link before closing the
browser window, or to read all feedback messages, or to fill out all
required fields that are marked required with an asterisk and painted
with a yellow background color. You won't be able to prevent users
from clicking twice on a button, a link, a check box, radio button,
etc.

That said, you might want to consider using a veil (see wicketstuff
minis). Or search the lists for veil.

Martijn

On Mon, Feb 28, 2011 at 6:01 PM, eugenebalt <eu...@yahoo.com> wrote:
> How do we prevent the user from double-clicking a non-Ajax component?
>
> When the submit occurs, isEnabled is set to "false" for the Wicket Button.
> If the user does a quick double click on the button, its throws a wicket
> runtime excpetion saying the component is disabled.
>
> Thanks
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/How-to-prevent-user-from-double-clicking-a-non-Ajax-component-tp3328308p3328308.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org