Re: event handler problem in large complex form

I think you are probably right. I worked on that assumption, and everything
now works ok. However I did find one or two other little bugs as I was doing
this, so not absolutely sure. Anyway, I have an approach now for avoiding
this problem in the future.

-- 
Arthur Rusdell-Wilson
"VK" <schools_ring@yahoo.com> wrote in message
news:1121186542.899613.91760@g49g2000cwa.googlegroups.com...
> > I find that in a large form (especially if there is a table within the
> > form?) that the form is submitted to my server-side script even when a
> > JavaScript 'onsubmit' event handler returns 'false'.
> > does any one else have this problem, and is there a work-round?
>
> I encountered it several times (but very rarely). It was always
> connected with too long delay before you approve/cancel the bubble.
> Always was helped by optimising the code (so your decision would come
> out quickly). One of undescribed yet ghosts of JavaScript (like orphane
> scripts). Never happens on primitive events like onclick/mousevove/etc.
>
> Form submission / window closure / unload - the most probable places to
> meet them. I call this "speedy bubbles", you may too if you want :-)
>
> I guess it's a part of interface protection, so you couldn't lock user
> on one page by simply putting each onsubmit/onbeforeunload/onload on
> some endless process. Just an amateur guess...
>
> Get the fat out of you script, it should help right away. Unless the
> problem is im something else.
>