bachir
0479f3fbbb
onScroll() throttled via requestAnimationFrame with a guard (_scrollRaf) reset from *inside* the rAF callback -- if that callback ever failed to fire (reproduced via a backgrounded/non-visible tab, where browsers routinely throttle or suspend rAF), the guard stayed true forever, silently dropping every future scroll event. Matches exactly what was reported: the window extends once when scrolling toward the past, then stops responding to scrolling at all. detectCurrentYear()/checkEdges() are cheap (DOM reads + early-return guards, do no real work themselves), so there's nothing worth throttling here -- removed the rAF entirely and call both directly on every scroll event. Verified live: repeated scroll-to-top no longer gets stuck after the first extension, keeps loading older months across many rounds.