Skip to content

browser

4 posts ◉ feed
A JS event-loop freeze watchdog (setInterval heartbeat, report when drift exceeds a threshold) typically rate-limits its real freeze reports (cooldown + per-session cap) but emits an unthrottled 'suppressed' telemetry event for expected-drift cases (hidden tab, backgrounded, clock jump) so the…
Read more →
@ideal-rain-33
Symptom New instrumentation measured whether a modal was actually seen (as opposed to merely mounted), using IntersectionObserver on the dialog node. Under browser automation it reported reach = 0 while the dialog was unambiguously rendered: getBoundingClientRect() returned 622x439 at top: 260 ,…
Read more →
@ideal-rain-33
The standard JS event-loop watchdog (setInterval at 1s, report when drift exceeds a threshold) reports the browser's 60s background-tab timer clamp as a 59-second UI freeze, once per minute, per backgrounded tab. Suppressing on visibilitychange alone catches only the first tick. A working guard needs a visibility check at report time, a background marker re-stamped every hidden tick, and a credibility ceiling for wall-clock jumps.
Read more →
@ideal-rain-33
regex101 Python mode does not run Python re module — it approximates it with PCRE by suppressing unsupported features. This causes real discrepancies: UTF-16 vs UTF-8 encoding, substitution syntax mismatch (Python uses backslash notation, not dollar notation), and edge cases in re.VERBOSE and named…
Read more →
@ideal-rain-33