Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

152
Views
Reverse Countdown timer when browser minimize

I am creating project using JavaScript. I have created a reverse timer in seconds. When the timer reaches zero then it will call some function.

This timer is working fine, but when the browser goes into sleep mode or is minimized then the timer is resume

setTimeout(() => {
  var counter = 60
  let updatedMsg;
  
  this.timer = setInterval(() => {
    counter--;
    if (counter == 0) {
      this.processLogout();
      clearInterval(this.timer);
    }
    console.log(counter)
    
    updatedMsg = message.replace("{0}", counter);
    messageRef.dialogRef.componentInstance.config.message = updatedMsg;
  }, 1000);
}, 500);
about 4 years ago · Juan Pablo Isaza
2 answers
Answer question

0

Below is the working solutions:

var startTime = new Date()
startTime.setTime(startTime.getTime() + 1000 * 120);
startTime = Math.floor(startTime / 1000);
function startTimeCounter() {
    var now = Math.floor(Date.now() / 1000); 

    var diff = startTime - now ; 
    var s = Math.floor(diff); 
    console.log(s)  
   
}
setInterval(() => {
  startTimeCounter()
}, 1000);
about 4 years ago · Juan Pablo Isaza Report

0

Instead of using a value that you increment/decrement when a callback is called, you should calculate when your countdown should finish. Then compare the current time against this target.

const MILLISECOND = 1;
const SECOND = 1000*MILLISECOND;
const MINUTE = 60*SECOND;
const finishAt = Date.now() + 1*MINUTE;
const intervalID = setInterval(() => {
  const now = Date.now();
  if (now < finishAt) {
    // code that is executed at a 1 second interval (if the browser is active)
    const msToGo = finishAt - now;
    const secToGo = Math.floor(msToGo / SECOND);

    console.log(secToGo);
  } else {
    clearInterval(intervalID);

    // code to be executed when your timer finishes
    console.log("done");
  }
}, 1*SECOND);

const MILLISECOND = 1;
const SECOND = 1000*MILLISECOND;
const MINUTE = 60*SECOND;

const finishAt = Date.now() + 10*SECOND;
const intervalID = setInterval(() => {
  const now = Date.now();
  if (now < finishAt) {
    // code that is executed at a 1 second interval (if the browser is active)
    const msToGo = finishAt - now;
    const secToGo = Math.floor(msToGo / SECOND);

    console.log(secToGo);
  } else {
    clearInterval(intervalID);

    // code to be executed when your timer finishes
    console.log("done");
  }
}, 1*SECOND);

Another option would be to create 2 callbacks. One that has a 1 second interval that executes some code at a specific interval. The other callback is a timeout that stops the interval.

const duration = 1*MINUTE;
const finishAt = Date.now() + duration;
const intervalID = setInterval(() => {
  // code that is executed at a 1 second interval (if the browser is active)
  const msToGo = finishAt - Date.now();
  const secToGo = Math.floor(msToGo / SECOND);

  console.log(secToGo);
}, 1*SECOND);

setTimeout(() => {
  clearInterval(intervalID);
  
  // code to be executed when your timer finishes
  console.log("done");
}, duration);

const MILLISECOND = 1;
const SECOND = 1000*MILLISECOND;
const MINUTE = 60*SECOND;

const duration = 10*SECOND;
const finishAt = Date.now() + duration;
const intervalID = setInterval(() => {
  // code that is executed at a 1 second interval (if the browser is active)
  const msToGo = finishAt - Date.now();
  const secToGo = Math.floor(msToGo / SECOND);

  console.log(secToGo);
}, 1*SECOND);

setTimeout(() => {
  clearInterval(intervalID);
  
  // code to be executed when your timer finishes
  console.log("done");
}, duration);

This second solution might drop an interval if the setTimeout() callback is executed before the final setInterval() tick. But in most scenarios this should not be an issue.

about 4 years ago · Juan Pablo Isaza Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!