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
After making it to work I realized that after severl scroll, if one click on a list item, open a new page and then hits Back, the list goes to the initial page loosing all items loaded with infinite scroll.
Any idea on how to force the browser to remember the new list?
The text was updated successfully, but these errors were encountered:
This is a known problem with all infinite scrolls. If you are using push state and caching results, you can avoid this. JQM should be remembering the list if you are using it to navigate between the pages instead of a normal HTTP request for every page.
On Mar 12, 2014, at 4:19 AM, claudiorivetti [email protected] wrote:
After making it to work I realized that after severl scroll, if one click on a list item, open a new page and then hits Back, the list goes to the initial page loosing all items loaded with infinite scroll.
Any idea on how to force the browser to remember the new list?
—
Reply to this email directly or view it on GitHub.
After making it to work I realized that after severl scroll, if one click on a list item, open a new page and then hits Back, the list goes to the initial page loosing all items loaded with infinite scroll.
Any idea on how to force the browser to remember the new list?
The text was updated successfully, but these errors were encountered: