[Proto-Scripty] Re: Ajax.PeriodicalUpdater not working in IE
On Oct 9, 8:57 am, asb ast.bha...@gmail.com wrote: Ajax.PeriodicalUpdater is not working in IE [9]. Tested in other browser its working. Help Needed Dear asb, I am sure that plenty of people here are willing to assist you, but is not working is usually not enough information to allows anybody to help you in efficient way (neither is is not working in IE [9]). Do you mean that : - it raises an execution error? (in this case, which error message do you get?) - it doesn't do what you expect it to do? (in this case, what does it do?) Also note that AFAIK the IE9 beta is not yet officially supported by prototype. If you try to use it already, you may need to put hands in the source (once again, if you give more information about what you're trying to do and what is actually happening, I am sure you will get some help for solving your issue). Best, Eric -- 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 prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
[Proto-Scripty] Prototype.js Memory Leaks
All, I'm a relatively new javascript programmer and like many I've successfully been able to implement prototype.js in a relatively complex application. However, the little expertise I have seems to have reached it's limits. I have an application which constantly adds, updates and deletes DOM elements. This can approach 100's of elements with each call. Some event handlers are attached. It typically does these adds, updates and deletes once once every 60 seconds. In an effort to monitor memory utilization in the browser I bumped it up to 5 seconds and in no time the memory consumed reaches epic levels. It basically forces the browser to come to a halt. The issue is that I'm not sure how to both track down the memory leak or inspect my code to which I can find the culprit. I'm wondering if this arena is a good starting point to ask for help. If I can get past this hurdle then I can continue to develop the application. Without getting past it the 6 months of work I've done thus far will be a waste :( Is there anyone who wouldn't mind helping and educating me? -- 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 prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.