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
I have observed several times that I could scroll to the end of a result page, scroll back up and down several times, and eventually, additional results would be loaded.
The text was updated successfully, but these errors were encountered:
I've added a help wanted label, because I'm not sure how to further improve this issue. It's been persisting for quite some time (see #31#89), and it's gotten better with performance improvements, but I think there's probably some fundamental architectural oversight.
In general, I think there's a discussion to be had on whether we should move to manual pagination and see if that improves performance.
It might indeed be that the triggering mechanism is used in a way it was not designed for. Replacing the trigger with a button or something at the end of the page would at least be an effective way to eliminate the scrolling effect's influence on any other potential issues.
I have observed several times that I could scroll to the end of a result page, scroll back up and down several times, and eventually, additional results would be loaded.
The text was updated successfully, but these errors were encountered: