Its easy when you are just dealing with "text elements" of equal size. But if you are loading images or injecting content in the list elements, the back-button starts to break.
Google’s suggestion for a better infinite scroll?
81–90 of 168 posts
Re: Google’s suggestion for a better infinite scroll?
#82One of my favorite features of infinite scroll is how it can make clicking on the footer of a page nearly impossible. E.g. try clicking on "About" or "Careers" on the bottom of http://venturebeat.com
You would be happy to live here in my town where the faster internet connection possible is 700kbps and you have plenty of time to click on footers of pages while the infinite scroll is loading.
Re: Google’s suggestion for a better infinite scroll?
#83StumbleUpon has been doing this for a couple of year. I always liked the built-in pagination.
Re: Google’s suggestion for a better infinite scroll?
#84I would feel kind of okay with infinite scroll if it wasn't creating memory problems. Especially on image-heavy (tumblr) / DOM-heavy (facebook) pages. If I browsed the web in 90s mode (one window, one page opened) that would maybe work, but when I have dozens of tabs opened, youtube playing in background and I start browsing an endless memory-hungry page, my laptop (3 GB RAM) starts dying. Another issue is the one me…
I also wonder about "memory problems", but of the soft kind. I like to consuming "pages" of content at a time, spread between many tabs. Usually I read to the bottom of a "page", and then switch tabs. When I come back to that tab, I'm ready to go to the next page. But with infinite scrolling, I feel like I'd be re-reading content to find my exact spot I left off..
That's a problem that can be solved by paginating the data and using the history api to push the page state on the stack while the UI seamlessly loads the pages together.
Re: Google’s suggestion for a better infinite scroll?
#85Love this. If only Hacker News and Reddit would implement it.
I don't even know how to get a second page of HN results. Never had the need. Infinite scrolling creates a daunting never-ending feeling. I like the sense of accomplishment after scanning/reading through a fixed list of results. Infinite scrolling makes that carrot forever out of reach.
It's the "more" link at the bottom.
Re: Google’s suggestion for a better infinite scroll?
#86So is there a way to use any of those devices coming out (including health monitoring!) without leaking everything to the cloud?
I'm getting really annoyed that none of those will actually give you the tools to dump your data yourself in total privacy.
(And no, I don't care how many step you had today!)
Re: Google’s suggestion for a better infinite scroll?
#87I don't think this fixes what is the core issue with infinite scroll: when I click into a subview and then press back, I am not returned to the same place where I was before. iOS, for instance, handles this extremely well by literally stacking the new view on top of the old one rather than changing the contents of the view. This implementation attempts to fix it, but only gets close, and so I have to re-contextualize myself every time I press back.
Re: Google’s suggestion for a better infinite scroll?
#88Re: Google’s suggestion for a better infinite scroll?
#89I'm surprised at how many people here seem to like infinite scroll. I personally can't stand it. Imagine having a book where no matter how much you read, it never seems to end. No milestones, no sense of progress. Just page after page after page. It just feels... icky.
Probably because of the inferiority complex the infinity characteristic imposes on you.
Makes you feel inadequate for not completing something.
It's ironic as it had already existed in a sense - with TV. It never ends either and powerfully attracts people to continue watching.
Re: Google’s suggestion for a better infinite scroll?
#90I would argue that Airbnb's old Infinity.js is way better than this. Smoother and has a fully functioning scrollbar still. This one's pretty janky imo.