Hi, > When creating an Ajax.Updater for instance if you use the method > onComplete in the Ajax.Options then it never unloads the Request from > the Ajax.Responders counter ....
Can you put together a small, self-contained test page demonstrating the issue, post it to Pastie[1], and link to it from here? If another set of eyes says it's a bug rather than (apologies) a misunderstanding, we'll want to raise a ticket for it on Lighthouse. [1] http:/pastie.org Thanks, -- T.J. Crowder tj / crowder software / com On Nov 14, 11:12 am, Jeztah <[EMAIL PROTECTED]> wrote: > Just to let everyone know i may have found a little bug in the > Ajax.Responders .. or maybe it is mean to to this way > > When creating an Ajax.Updater for instance if you use the method > onComplete in the Ajax.Options then it never unloads the Request from > the Ajax.Responders counter .... > > If you dont use onComplete in your options then it does ... > > Strange behaviour it seems as i was wondering why something was > keeping my Request count high on a page when it should be unloaded and > removed from the pool > > If its not a bug someone may have been scratching thier head for an > hour like me trying to figure it out .. > > In my case i was creating an activity display to show me when Ajax > calls were being made on a page > > Regards > Alex --~--~---------~--~----~------------~-------~--~----~ 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-scriptaculous@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
