I'd guess that your focus listener is getting called when everything is starting up. You could try checking if you have a carouselIntervalId before starting the timers.
I'd guess that your focus listener is getting called when everything is starting up. You could try checking if you have a carouselIntervalId before starting the timers: if(!carouselIntervalId) carouselIntervalId = setInterval(...); And since we're all properly paranoid here, put that check before both setInterval calls. Then you'd want to nullifying carouselIntervalId when you stop the timer: if(carouselIntervalId) clearInterval(carouselIntervalId); carouselIntervalId = null; You'd want the above around all clearInterval calls of course.
Also, while I have your attention (?), I notice that you have two different setInterval calls: setInterval(function() { carouselNext() }, 15000); // And later... setInterval(function() { if (animate == true) { carouselNext() } }, 15000); You might want to make them the same to avoid confusion and bugs.
2 I can verify in the IE debugger that the code is setting two interval timers upon startup - one in your intialization and one in the initial focus event. The fix would be as mu said to not set a new interval if one is already running. – jfriend00 Jul 24 at 6:57 @jfriend00: Thanks, I didn't want to drag out my IE testing gear.
– mu is too short Jul 24 at 7:04 checking for carouselIntervalId seems to have done the trick. It was somehow stuck in the back of my mind that setting a new value for carouselIntervalId would simply delete the old interval and replace it with a new one. – stefanvignir Jul 24 at 17:41.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.