github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #8356] [MERGED] docs: fix layout bugs related to the TOC #16166

New Issue
Closed
opened 2026-04-13 10:25:09 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 10:25:09 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/8356
Author: @bytaesu
Created: 3/4/2026
Status: ✅ Merged
Merged: 3/4/2026
Merged by: @bytaesu

Base: canary ← Head: cursor/docs-toc-scroll-conflict-41e3

📝 Commits (3)

  • 066413d fix(docs): prevent scroll-chaining between TOC scroll area and page
  • 1f35ccc fix TOC related codes
  • 0372715 Merge branch 'canary' into cursor/docs-toc-scroll-conflict-41e3

📊 Changes

5 files changed (+28 additions, -300 deletions)

View changed files

📝 landing/app/blog/[[...slug]]/page.tsx (+0 -6)
📝 landing/app/globals.css (+27 -23)
📝 landing/components/docs/docs-sidebar.tsx (+1 -1)
➖ landing/components/docs/group-toc-items.tsx (+0 -16)
➖ landing/components/docs/stepper-toc.tsx (+0 -254)

📄 Description

Add overscroll-behavior-y: contain to the TOC scroll area to prevent erratic scrolling caused by scroll chaining with the page.

When the Table of Contents (TOC) is long enough to create its own scroll area, the browser's default scroll-chaining behavior causes scroll events to leak between the TOC container and the main page. This results in unpredictable and jittery scrolling, as reaching the boundary of one scroll area causes the other to jump. Adding overscroll-behavior-y: contain isolates the TOC's scroll container, preventing this propagation.

Slack Thread

Open in Web Open in Cursor 

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/8356 **Author:** [@bytaesu](https://github.com/bytaesu) **Created:** 3/4/2026 **Status:** ✅ Merged **Merged:** 3/4/2026 **Merged by:** [@bytaesu](https://github.com/bytaesu) **Base:** `canary` ← **Head:** `cursor/docs-toc-scroll-conflict-41e3` --- ### 📝 Commits (3) - [`066413d`](https://github.com/better-auth/better-auth/commit/066413dda9b62d42de6e8a525943fcd7be2deb21) fix(docs): prevent scroll-chaining between TOC scroll area and page - [`1f35ccc`](https://github.com/better-auth/better-auth/commit/1f35ccc4d4727c8439153e4c787aa2ffdd4c254f) fix TOC related codes - [`0372715`](https://github.com/better-auth/better-auth/commit/0372715292c25fcbf39e4ff88632a6932b0c7852) Merge branch 'canary' into cursor/docs-toc-scroll-conflict-41e3 ### 📊 Changes **5 files changed** (+28 additions, -300 deletions) <details> <summary>View changed files</summary> 📝 `landing/app/blog/[[...slug]]/page.tsx` (+0 -6) 📝 `landing/app/globals.css` (+27 -23) 📝 `landing/components/docs/docs-sidebar.tsx` (+1 -1) ➖ `landing/components/docs/group-toc-items.tsx` (+0 -16) ➖ `landing/components/docs/stepper-toc.tsx` (+0 -254) </details> ### 📄 Description <!-- CURSOR_AGENT_PR_BODY_BEGIN --> Add `overscroll-behavior-y: contain` to the TOC scroll area to prevent erratic scrolling caused by scroll chaining with the page. When the Table of Contents (TOC) is long enough to create its own scroll area, the browser's default scroll-chaining behavior causes scroll events to leak between the TOC container and the main page. This results in unpredictable and jittery scrolling, as reaching the boundary of one scroll area causes the other to jump. Adding `overscroll-behavior-y: contain` isolates the TOC's scroll container, preventing this propagation. --- [Slack Thread](https://betterauth.slack.com/archives/C0A8B5BARUK/p1772579636468119?thread_ts=1772579636.468119&cid=C0A8B5BARUK) <p><a href="https://cursor.com/agents/bc-724615f5-0d42-548d-b923-0fc16277d776"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-724615f5-0d42-548d-b923-0fc16277d776"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</p> <!-- CURSOR_AGENT_PR_BODY_END --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 10:25:09 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#16166
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?