authorgravatar for saphid@gmail.comAlex Southwell <saphid@gmail.com> 2026-09-12 13:16:01+10:00
committergravatar for noreply@github.comGitHub <noreply@github.com> 2026-09-12 00:16:01-03:00
log38827789c4de97955315b459cb3b0b8207f692d8
treeb3b7d1fbd0d26e49da273de562a767227d2566fe
parentefccda9ac9230db22b36990cffabdad218fa41b0
signature Signed by PGP key B5690EEEBB952194

fix(web): keep sidebar scroll position when pinning threads (#10757)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

2 files changed, 5 insertions(+), 1 deletions(-)

apps/web/src/components/ui/sidebar.tsx+2-1
......@@ -706,8 +706,9 @@ function SidebarContent({
706706 className="h-auto min-h-0 flex-1"
707707 >
708708 <div
709 // Reordered rows must not pull the viewport to their new position.
709710 className={cn(
710 "flex w-full min-w-0 flex-col gap-2 group-data-[collapsible=icon]:overflow-hidden",
711 "flex w-full min-w-0 flex-col gap-2 [overflow-anchor:none] group-data-[collapsible=icon]:overflow-hidden",
711712 className,
712713 )}
713714 data-sidebar="content"
docs/user/thread-sidebar.md+3
......@@ -29,6 +29,9 @@ the thread opens and the files are attached in its composer, ready for
2929your next message. The same per-message file limits apply as when attaching
3030files directly; see [Attach files](./composer.md#attach-files).
3131
32On web and desktop, pinning or unpinning a thread keeps the sidebar at your current
33scroll position instead of following the thread to its new place in the list.
34
3235Pinning does not prevent automatic settlement. Settling a thread removes its pin.
3336
3437On web and desktop, drag a thread between sections to change its state. Drag a thread up into