J

Bummer this issue has not been addressed after a year and a half... pretty important feature for a markdown renderer.

This would be great; is this project inactive?

Ever figure this out?

Any chance someone could review this? It's a pretty minor addition...

> Why stores? Couldn't it be as simple as this? > > ```ts > const [scroll, setScroll] = solid.createSignal(null) > solid.onMount(() => mo.scroll(setScroll, options)) > return scroll > ``` >...

The reason I didn't use stores is to allow destructuring like this `const { time, scrollX, scrollY } = useScroll()`, for convenience. It's been almost a month, any chance this...

> Another option what would keep the same api but not require bringing in stores: > > ```ts > > const [time, set_time] = createSignal(0) > > const [x_current, set_x_current]...

I tried to provide a way to access `scrollToItem` from the `VirtualList` component, but after doing a bit of searching I couldn't seem to find any documentation on idiomatic ways...

Alright, I fixed the issue with reactivity being broken by not unwrapping accessors at the top level of `createVirtualList`. Would still like some help with exposing `scrollToItem` properly outside of...