Never seen anything like that. It would be basically impossible for
Ajax.Updater to do that. The only thing that comes to mind is if
you're using submit buttons or similar to trigger the Ajax.Updater
operation and in some strange situations, you're not cancelling the
default action of the button. E.g., like this:


    <input type='text' id='txtCriteria'>
    <input type='submit' value='Search' id='btnSearch'>


    $('btnSearch').observe('click', function(event) {
        // Some logic here

        // We've handled it, stop the event

In the above, suppose something blows up in `doSomethingElse` because
of some special weird state the page has gotten itself into. That
means you're not stopping the event (since the stop is at the bottom,
but the exception's happened above it), so the form gets submitted --
reloading the page.

That's the kind of thing I'd be looking for. It's not going to be
actually _in_ Ajax.Updater if you follow me.

T.J. Crowder
Independent Software Consultant
tj / crowder software / com

On Jul 28, 4:29 pm, "reuben.m" <reube...@gmail.com> wrote:
> 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 results in a normal http request being made, and
> as a result, the entire web page is re-sent rather than just the inner-
> html content.
> I have no idea what is causing it. It is not easily reproducible, and
> seems to happen at random. I've had people reporting this happening on
> both Firefox and IE8.
> This is a rails app, with prototype 1.6.1.
> Any suggestions? I haven't been able to reproduce it personally, but I
> have observed it on somebody else's computer where I installed Firebug
> with the net extension so that I could monitor the XMLHttpRequests.
> One idea that came to me last night was that it might possibly be
> something to do with that buggy .NET addon. I got rid of it, but it
> was present on the computer where I was able to observe this
> happening, and any problems with it are probably present in IE8 as
> well. I know that addon has caused problems with communication in the
> past, so I thought I might look into that.
> But if anybody has any suggestions, or has seen similar issues
> elsewhere, please let me know.

You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptacul...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to