Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

measureElement caches 0 size for nodes that aren't attached yet (Vue: rows stack at start 0 and the list scrolls away on mount)

Aperta Adatta ai principianti
  • Qualcosa non va?
#1,292 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
frontend, performance

Direzione di ricerca

Inizia da Virtualizer.measureElement e confronta il suo percorso di misurazione sincrono con la gestione esistente di ResizeObserver per i nodi disconnessi. Verifica che i nodi scollegati mantengano la loro dimensione stimata mentre continuano a essere osservati, quindi aggiungi o esegui un test di regressione che copra la misurazione dei nodi scollegati, la successiva connessione e il mantenimento della posizione di scorrimento.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

Virtualizer.measureElement(node) measures the node synchronously right after observing it, even when the node is not attached to the document yet. A detached node reports offsetHeight === 0, and since there is no cached size on the first measurement, that 0 is stored as the item size.

In Vue this is easy to hit. Function refs run synchronously during patch, so when the rows are created in the same patch as their parent (the sizer is behind v-if and shows up once data is loaded), :ref="(el) => virtualizer.measureElement(el)" is called while the sizer is still detached:

  1. Every visible row gets size 0 and renders at start: 0, on top of each other.
  2. On the next frame the ResizeObserver reports the real sizes and the rows spread out.
  3. The list ends up scrolled down (~305px in the repro, row 9 at the top) instead of staying at the top.

The ResizeObserver callback already ignores disconnected nodes (#1135), but the sync path in measureElement doesn't. #1226 only rejects a 0 when there is a previously cached size, so it doesn't cover the first measurement either.

Your minimal, reproducible example

https://stackblitz.com/github/webn00b/tanstack-vue-virtual-detached-measure

Steps to reproduce
  1. Open the repro. The scroll container is always rendered; the sizer and the rows are behind v-if="loaded", which flips after a simulated fetch.
  2. Rows are measured with :ref="(el) => virtualizer.measureElement(el)", estimateSize is 60.
  3. Check the output under the list: the ref calls log isConnected: false, offsetHeight: 0, and right after nextTick the visible items have start: 0, size: 0.
  4. After the ResizeObserver fires, the list is at scrollTop ≈ 305.
Expected behavior

Rows keep their estimateSize positions until they are measured, and the list stays at scrollTop: 0.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform
  • OS: macOS
  • Browser: Chrome

Not browser-specific, it comes from when Vue calls function refs.

tanstack-virtual version

@tanstack/vue-virtual 3.13.39, @tanstack/virtual-core 3.17.11

TypeScript version

No response

Additional context

Skipping the sync measurement when !node.isConnected fixes it. The node is still observed, so the first frame uses estimateSize, the ResizeObserver delivers the real size once the node is attached, and the scroll position stays at 0. I have a fix with a regression test and can open a PR.

Terms & Code of Conduct
  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Lingua principale
TypeScript
Stelle
7.1k
Fork
468
Merge medio
1g 2h
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TanStack/virtual

Tutte le issue di TanStack/virtual

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.