Why Do YOU WILL NEED 25 Timers?
Countdown Timers SLOWING Page: How to create multiple running countdown timers for an individual page? I’m attempting to make a website that has multiple countdown timers running on the web page simultaneously, including displaying the milliseconds possibly. So far I’ve been using setInterval() functions, but after having simply a few setIntervals() running, the page starts slowing down, the seconds start slowing down and lagging, etc. and it generally does not work.
With no lag or problems? I want to have maybe 25 countdown timers all running on the web page simultaneously, without slowing the web page, or having to send a huge selection of requests per-second to the server? I’m attempting to make a personal TO ACCOMPLISH app that models timers for every task, day and I want to see the timers running for all tasks for the entire. Why do you need 25 timers?
Can’t you just have one setInterval, and enhance 25 different factors? I would begin using second.js, as it creates your time and effort with javascript super fast. Now, whenever a task is created by you, you store the timestamp of when it will expire using second.js. You then have a worldwide timer that has got the right time every second.
Going in milliseconds is a negative idea because the function loop will decelerate time itself in the application. This global timer will flames functions that update each job timer, comparing the existing time with the duty expiry time. No need for 25 timers! Just one …