useScrollToBottom (user-message-anchor) undershoots on thread load — lands several messages before the last user message

Abierto
  • ¿Algo no está bien?
#412 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@abhithesys ya está trabajando en esto.

Desde el 28/3/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug

Bug Report: useScrollToBottom with user-message-anchor doesn't reach the last user message on thread load

Package versions
  • @openuidev/react-ui: 0.9.20
  • @openuidev/react-headless: 0.7.11
  • React: 19.2.4
Describe the bug

When loading a thread with many messages (via loadThread), the scroll
position lands several messages before the last user message instead of
placing it at the top of the viewport. The user must manually scroll down
to reach the end of the conversation.
The desired behavior — last user message pinned to the top of the
viewport — is correct; it's just not being achieved.

AI Analysis

The user-message-anchor branch in useScrollToBottom (lines 76-89)
does the right thing in principle:

const lastUserMessageDiv = Array.from(
  element.querySelectorAll(userMessageSelector)
).pop();
const scrollPosition =
  lastUserMessageDiv.getBoundingClientRect().top -
  element.getBoundingClientRect().top +
  element.scrollTop;
element.scrollTo({ top: scrollPosition, behavior: "smooth" });

The scroll fires in the useEffect on line 93-103 the moment isLoadingMessages flips to false. The issue is that at that point the message components haven't finished laying out — complex content like OpenUI components, Markdown blocks, tool-call accordions, and images are still mounting and expanding. As a result:

getBoundingClientRect() returns stale geometry — the positions are based on partially-rendered content, so the calculated scrollPosition is too low (too far up in the chat).

behavior: "smooth" locks in the stale target — the animated scroll commits to the position computed at call time. As content continues to expand below the measurement point the target becomes increasingly wrong, but smooth scroll doesn't re-evaluate.

Together these cause the scroll to land several messages short of the actual last user message.

Steps to reproduce

  • Use Shell.ScrollArea with the default scrollVariant ("user-message-anchor").
  • Have a thread with ~20+ messages, ideally containing assistant responses with rich content (OpenUI Renderer output, Markdown with code blocks, tool calls).
  • Load the thread (click it in the sidebar → loadThread).
    Observe: the viewport lands a few messages above the last user message. Scrolling down manually reveals the remaining messages.

Expected behavior

The last user message should be positioned at the top of the viewport after the thread finishes loading.

Lenguaje dominante
TypeScript
Estrellas
10k
Forks
698
Merge medio
1 d 3 h
PR fusionados (30 d)
133

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de thesysdev/openui

Todos los issues de thesysdev/openui

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.