I've created a web app using prototype's Ajax class to do most of the
heavy lifting. The initial web page only loads once and from then on
everything is manipulated with XMLHttpRequests. (Mostly POST requests)
The problem I'm running into is that every once in a while, the
Ajax.Updater somehow res
That's something I hadn't thought of... I do occasionally run into
"element,parentNode is null" errors where an element is trying to be
accessed after it's already gone from the DOM. After that javascript
either stops working or stops working correctly, so maybe that is
causing problems with form s
ctionality in the process. (Is there a way to select
only the top-most elements when deleting all elements of a class?) Now
I'm just hiding them instead since they don't present problems when
hidden.
We'll see if that fixes the issue. If not I'll post back.
On Jul 28, 11:19 a
Ok, I posted a thread a week or two ago about how I was having random
and hard to reproduce problems with Ajax.Updater where the response
would be to a standard post request rather than an XHR request. The
full page returned would get stuck in the innerHTML and everything
would fall apart.
So I've
Also, I was thinking this might be because the "return false" was not
coming quick enough to stop the standard form action. If I call it
synchronously, will it prevent the default action from being processed
until the javascript call completes?
On Aug 5, 12:49 pm, "reuben.m&q
gt; Rails forum instead.)
>
> Bottom line is that if you really do stop the submit event, it will
> not happen. Something is preventing the submit event from being
> stopped.
>
> FWIW,
> --
> T.J. Crowder
> Independent Software Consultant
> tj / crowder software / comww
