Hi there, Firstly, I apologise if this is hidden somewhere in the documentation, but I assure you I've read through it all and couldn't see anything relating to this. I am new to prototype, and am slowing getting to grips with it (and JS in general).
Today I had a user report to me that they are seeing the results of the OnLoading event handler *after* the OnComplete. By this, what I mean is that I simply have a textarea field on a page, of which the contents are pulled using a prototype GET request. They see "Loading..." as I have specified from the OnLoading handler. They then see the relevant text in the textarea, and then it seems to somehow go back to OnLoading extremely quickly, all in a flash. Either that, or for some reason OnLoading is kicking in *after* OnComplete has finished. I have only managed to reproduce this once, and now I can't :/ Is there any particular order in which you are meant to specify OnEvent handlers? Should OnComplete come BEFORE OnLoading? Anyone have any ideas what the problem may be? Thanks in advance, Rich. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
