vue-virtual-scroller
vue-virtual-scroller copied to clipboard
Only last 2 items are visible after using "page-mode", and also elements not rendering correctly.
After adding page-mode attribute, rendering the data on view is not working as expected. Without using page mode everything is working correctly.`

without page mode, same question
Same here, when using page-mode, scrolling down doesn't render new elements (just empty space), yet the scrollbar is correctly sized.
Without page-mode, no issue. I guess it's a problem with the observer and specific layout we have in our projects.
Could one of you make a sample project that replicates the issue so I can get a better look at the issue?
hello, we are also experiencing this issue using page-mode. do we have an update on this one ?
For me the issue was using overflow-y:visible;overflow-x:hidden;
on an element in the dom above the virtual scroller. in computed the overflow-y:visible
will be set as overflow-y:auto
.
The scrollparent
package will then detect the element with the overflow-y:auto
and not the actual body, html
.
Instead use just overflow: visible
.
Wrong:
<html>
<body>
<div class="main-wrapper" style="overflow-y:visible;overflow-x:hidden">
<DynamicScroller></DynamicScroller>
</div>
</body>
</html>
Correct:
<html>
<body>
<div class="main-wrapper" style="overflow:visible;">
<DynamicScroller></DynamicScroller>
</div>
</body>
</html>
but im still having weird spacing issues, at least the elements are rendering now.
Have the same issue, I'm using Vue 3 and the current Beta of vue-virtual-scroller (2.0.0-beta.8)
https://github.com/Akryum/vue-virtual-scroller/assets/17964384/cf1e766b-4531-4560-aba1-065eebbbcc22
My Project on Github: https://github.com/felix-berlin/berliner-schnauze
Live URL: https://berliner-schnauze.wtf/
Same issue. I'd like to page-mode
look for the closest overflow-y: auto
element and use it as its reference. I noticed that the position at which rendering is triggered seems affected by the presence of static content above the virtual scroller. In particular, if the static content is taller, the rendering will occur only after scrolling further.