Countdown timing is inaccurate about flipclock HOT 3 CLOSED

I just tested this exact example for 5 minutes, and mine was only a few seconds behind. I noticed my clock didn't get out of sync until I left one browser to in the background and did other stuff while the clock runs... I am not sure what would cause this considering I am using the system time and just passing the number of seconds that have passed to the clock, and it just performs a flip. It's almost as if this is a cpu/browser issue. I am not sure how to fix it off the top of my head.

from flipclock.

Hi Justin,

I love your app by the way.

I'm going to have to resort to the most accurate option. Here is what I
found. The code below is a simple countdown timer that runs an interval and
constantly finds the current time difference and refreshing the html.

I hope this helps in some way. Thanks for your reply.

window.onload = function() {

var minutes, seconds;

var countdown = document.getElementById("countdown");
var target_date = new Date(new Date().getTime() + (25*60000))

setInterval(function () {

var current_date = new Date()

var seconds_left = (target_date - current_date.getTime()) / 1000;

minutes = parseInt(seconds_left / 60);
seconds = parseInt(seconds_left % 60);

// format countdown string + set tag value
countdown.innerHTML = minutes + "m, " + seconds + "s";
}, 1000);

};

from flipclock.

That's pretty much the same thing I do. At this point I will just keep an eye on this, because I am not sure how to fix it. If anyone else has any insight, just let me know.

from flipclock.