Time measurement in computing presents unique challenges that distinguish digital timers from their mechanical counterparts. At the heart of browser-based timing lies the JavaScript event loop and the various timing APIs available to web applications. The most fundamental is setTimeout and setInterval, which schedule callbacks after a specified delay, but these are not precision instruments. The HTML specification allows browsers to throttle timers to a minimum of 4 milliseconds for nested timeouts and, critically, to 1000 milliseconds or more for background tabs to conserve battery and CPU resources.

For high-precision timing, modern browsers provide the Performance API through performance.now(), which returns a DOMHighResTimeStamp measured in milliseconds with microsecond precision. Unlike Date.now(), which is subject to system clock adjustments and can actually move backward during NTP synchronization, performance.now() is based on a monotonic clock that always advances forward at a consistent rate. This makes it the preferred choice for measuring elapsed time in stopwatch applications where accuracy matters.

The requestAnimationFrame API plays a complementary role in timer applications. While not a timing mechanism itself, requestAnimationFrame synchronizes visual updates with the browser's repaint cycle, typically running at 60 frames per second (approximately 16.7 milliseconds per frame). For a stopwatch display that updates continuously, using requestAnimationFrame ensures smooth visual updates without wasting CPU cycles on off-screen rendering. The callback receives a high-resolution timestamp that can be used to calculate the exact elapsed time, combining precise measurement with efficient display updates.

Background timer behavior is a significant consideration for web-based timing tools. When a browser tab loses focus, most browsers reduce timer frequency to conserve resources. Chrome throttles setInterval to once per second for background tabs, and may further reduce to once per minute for tabs that have been hidden for extended periods. The Page Visibility API (document.visibilityState) allows applications to detect when they move to the background and compensate by recording the time of the visibility change and calculating the correct elapsed duration when the tab becomes visible again. Web Workers provide another solution, as timers running in a Worker thread are not subject to the same throttling as main-thread timers, enabling more reliable background operation. The Notification API enables browser notifications that function even when the tab is not active, ensuring countdown completion alerts reach the user regardless of which tab or application has focus.