Indeed I did misunderstand your intent, then.
-Mike
On 4/12/06, Bryan Lewis <[EMAIL PROTECTED]> wrote:
> I'm not sure it helps him either, except maybe in understanding why
> three clicks turned into two method calls. The tweak on the client
> machine was only a debugging trick.
>
>
> Mike Snare
I'm not sure it helps him either, except maybe in understanding why
three clicks turned into two method calls. The tweak on the client
machine was only a debugging trick.
Mike Snare wrote:
>Not sure that helps him. It's not feasible to expect people to tweak
>their OS settings to fit your app,
Not sure that helps him. It's not feasible to expect people to tweak
their OS settings to fit your app, so we have to fix it on our side.
Unless I misunderstood your intent...
-Mike
On 4/12/06, Bryan Lewis <[EMAIL PROTECTED]> wrote:
> The operating system will combine fast double clicks into a
The operating system will combine fast double clicks into a single
event. When I've had to test such things on a Windows client machine, I
went into the mouse control-panel widget and upped the double-click
speed so that I could click twice before the page went away, but without
my sequence being
When I want to cancel the submission of a form in tapestry via
javascript I set the event's abort and cancel_handlers properties
appropriately.
tapesty passes your ${checkSubmit} method an event 'object' that has
the above mentioned properties.
returning false from a handler like this won't have
Seems like a race condition. Why not just disable the button in the
onClick? You could start a timer to re-enable it if you needed to, but
if the page redisplays then just leave it alone.
-Mike
On 4/12/06, Dan Adams <[EMAIL PROTECTED]> wrote:
> Okay, I've got the common problem where I want to p
actually, sorry to bother you, but did you work out something this
simple to support a "submit on enter" for textfields?
Dan Adams wrote:
Okay, I've got the common problem where I want to prevent some users
from double clicking submit buttons and double submitting a form. I've
got the following
once you get this working, could you submit a patch against the main
form component to support this through a simple parameter?
Dan Adams wrote:
Okay, I've got the common problem where I want to prevent some users
from double clicking submit buttons and double submitting a form. I've
got the fo
Okay, I've got the common problem where I want to prevent some users
from double clicking submit buttons and double submitting a form. I've
got the following script which seems to work except that it seems to
miss one of the clicks. If you double click, it still double submits the
form. If you trip
