looking into it, thanks

hey @zarko-tg, either that bug existed for ever or something changed in how chrome performs rendering internally. Anyway, i've figured out what's the issue.

With your example, the first two items aren't rendered on the first paint, as the range is something like 3:28. If you scroll up, rxFor creates the new views (+ attaching them as children to the DOM). The layout is now unstable - new nodes were added. Next, the scroll strategy asks for the dimensions of the newly created nodes which triggers a forced reflow - the layout will be stabilized. Before the scroll strategy does set position: absolute, chrome already rendered the node as position: relative, increasing the size of the scroll viewport and pushing down other nodes.
That's how the scroll position gets weirdly out of sync.

In order to fix it, i've just enforded an absolute positioning for child nodes of the __runway.