You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2020. It is now read-only.
I'm not 100% on this, but I'm noticing un-rendered white flashes when scrolling upward, and increasing rowPadding doesn't seem to help. It does seem to help with white flashes when scrolling downward.
So, my guess is that the extra rows are only being rendered below the viewport, not above.
I had some trouble following all the math in virtual-each/component.js, but I got the impression that my guess is right.
Would you be open to rendering the extra rows around the viewport instead? It will introduce some more complexity to the scroll state around the top/bottom of the list.
The text was updated successfully, but these errors were encountered:
Unsure I follow adding padding around viewport. Could you screen grab what you are seeing? (http://www.cockos.com/licecap/ If you need an app for this)
As you can see, the 10 rowPadding rows are rendered below the viewport, so scrolling down doesn't show a white flash. But no extra rows are rendered above the viewport, so scrolling up shows a white flash.
A rowPadding of 10 should probably render 5 above and 5 below, or 10 above and 10 below, rather than just 10 below.
I'm not 100% on this, but I'm noticing un-rendered white flashes when scrolling upward, and increasing
rowPadding
doesn't seem to help. It does seem to help with white flashes when scrolling downward.So, my guess is that the extra rows are only being rendered below the viewport, not above.
I had some trouble following all the math in
virtual-each/component.js
, but I got the impression that my guess is right.Would you be open to rendering the extra rows around the viewport instead? It will introduce some more complexity to the scroll state around the top/bottom of the list.
The text was updated successfully, but these errors were encountered: