Fix table-of-contents page group's first item cut off after navigation (RND-11314)#4391
Open
zenoachtig wants to merge 3 commits into
Open
Fix table-of-contents page group's first item cut off after navigation (RND-11314)#4391zenoachtig wants to merge 3 commits into
zenoachtig wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: 39bdbd0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
The collapsible-groups change drives the sticky group header's fade gradient from an IntersectionObserver, but treated the sentinel leaving the viewport as "stuck" — which also happens when a group is below the fold or transiently mid client-side navigation. That lit the gradient (which overlaps the group's first item) for not-stuck groups, and the compositor could leave it painted over the first item as a stale layer. Only mark the header stuck once the sentinel has scrolled above the scroll area's top. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
zenoachtig
force-pushed
the
claude/tender-allen-bxkq9b
branch
from
July 14, 2026 15:45
a41d140 to
f46841f
Compare
zenoachtig
marked this pull request as ready for review
July 14, 2026 15:55
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
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.
Linear issue: https://linear.app/gitbook-x/issue/RND-11314
Overview
Root cause
The collapsible-groups work (#4177) drives each sticky group header's fade gradient (an
::afterband attop-full h-4, overlapping the group's first item) from anIntersectionObserveron a sentinel. It marked the header stuck whenever the sentinel stopped intersecting — but that also happens when:So the fade gradient switched on for groups that aren't actually pinned, and the compositor could leave it painted over the first item as a stale layer. It's always the first item because that's exactly what the gradient overlaps.
Fix
Mark the header stuck only once the sentinel has actually scrolled above the scroll area's top, instead of on any non-intersection:
Verification
Verified against the live affected site by attaching a real
IntersectionObserverwith the new condition:Typecheck and Biome format are clean on the change.
Manual check
…/asdf).Changelog
— Authored by Claude