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
When navigating back, I observe that all previously appended results are gone, and I end up scrolled back to the top where the first set of results are shown.
Is it possible to keep all the models, and when going "back", I go back to the page including all appended and autoloaded records?
Current behavior
Visit infinity page, initially 50 items
Scroll down
Load a bunch of new pages; say 250
Click item 250 - this changes route
Go back to the previous page
Only first 50 items are shown
Trying to achieve the following:
Visit infinity page, initially 50 items
Scroll down
Load a bunch of new pages; say 250
Click item 250 - this changes route
Go back to the previous page
250 items are shown, scrolled down
The text was updated successfully, but these errors were encountered:
Going "back" to an infinite scroll list after clicking on an item also causes OSX Safari to freeze for some seconds, and show number 200+ while secretly being reset to the first results. So if you click on (for example) number 240, it will open number 40 as if you clicked on 40. Safari Version 12.1 (14607.1.40.1.4)
the infinityModel method always assumes that you're starting from 0.
Perhaps a shouldFlushInfinityModel hook (or similar) could be the solution here! If you'd like to take a stab at that, we'd very much appreciate it.
So Safari has this back/forward cache that when going back always assumes you're starting from exactly the state where you left off. How do other people deal with this?
When navigating back, I observe that all previously appended results are gone, and I end up scrolled back to the top where the first set of results are shown.
Is it possible to keep all the models, and when going "back", I go back to the page including all appended and autoloaded records?
Current behavior
Trying to achieve the following:
The text was updated successfully, but these errors were encountered: