Make the section links actually arrive, not just navigate - #632
Merged
Conversation
The previous commit got the header off a routed page and onto the homepage, but
the reader still landed at the top rather than at the section they clicked. Two
causes, found by instrumenting rather than guessing again:
- The polling used requestAnimationFrame, which is throttled to zero frames in a
hidden or backgrounded tab. A correctness path must not be built on the
animation clock; it now uses a timer.
- scrollIntoView({behavior: 'smooth'}) is itself animation-driven and silently
does nothing under the same conditions — measured: the element sat at
top: 4041 for three seconds while scrollY stayed at 7, and behavior: 'auto'
moved it instantly.
Behaviour is now chosen rather than assumed: instant when the document is hidden
or the reader has asked for reduced motion, smooth otherwise. Arriving instantly
beats not arriving.
Verified all eight header links from a routed page and from the homepage, plus
the footer, and checked that #/quantum and the external docs link are unaffected.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions Bot
added a commit
that referenced
this pull request
Aug 8, 2026
Make the section links actually arrive, not just navigate (#632) The previous commit got the header off a routed page and onto the homepage, but the reader still landed at the top rather than at the section they clicked. Two causes, found by instrumenting rather than guessing again: - The polling used requestAnimationFrame, which is throttled to zero frames in a hidden or backgrounded tab. A correctness path must not be built on the animation clock; it now uses a timer. - scrollIntoView({behavior: 'smooth'}) is itself animation-driven and silently does nothing under the same conditions — measured: the element sat at top: 4041 for three seconds while scrollY stayed at 7, and behavior: 'auto' moved it instantly. Behaviour is now chosen rather than assumed: instant when the document is hidden or the reader has asked for reduced motion, smooth otherwise. Arriving instantly beats not arriving. Verified all eight header links from a routed page and from the homepage, plus the footer, and checked that #/quantum and the external docs link are unaffected. Co-authored-by: Dmitrii Vasilev <admin@t27.ai> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous commit got the header off a routed page and onto the homepage — but the reader still landed at the top, not at the section they clicked. Two causes, found by instrumenting rather than guessing again:
requestAnimationFrame, throttled to zero frames in a hidden or backgrounded tab. A correctness path must not be built on the animation clock; it uses a timer now.scrollIntoView({behavior: 'smooth'})is itself animation-driven and silently does nothing under the same conditions. Measured: the element sat attop: 4041for three seconds whilescrollYstayed at 7, andbehavior: 'auto'moved it instantly.Behaviour is now chosen rather than assumed — instant when the document is hidden or the reader asked for reduced motion, smooth otherwise. Arriving instantly beats not arriving.
Verified all eight header links from a routed page and from the homepage, plus the footer, and confirmed
#/quantumand the external docs link are unaffected.🤖 Generated with Claude Code