11–20 of 39 posts
Infinite scrolling is typically annoying, often making you do busy work to find content you want, and frankly a worse solution than just having multiple pages. So if it's also harder, why do it?
Infinite scrolling is typically annoying, often making you do busy work to find content you want, and frankly a worse solution than just having multiple pages. So if it's also harder, why do it?
Thank you. Infinite scroll sucks.
Especially when it's a list like favorites where you would what to browse to any point equally as often (im looking at you SoundCloud).
I'm hoping that infinite scroll looses the hipster appeal sooner or later and we can implement the best solution rather than jumping on the bandwagon all the time (SoundCloud's favorites were paginated a few years ago).
I attempted to prototype what it would be like loading the space in the full viewport so you can have an accurate scroll bar. It uses lazy loading with a deliberate 1 second delay server side. http://www.meda.co.uk/sandbox/infinitescroll/list.php Fun project, but very challenging to make it work it fast on a mobile device. Basically it adds placeholder elements and adds the items when they get close to the viewport.…
Is it me or is it impossible to scroll that page in Safari?
Infinite scrolling is typically annoying, often making you do busy work to find content you want, and frankly a worse solution than just having multiple pages. So if it's also harder, why do it?
I'd rather infinite scroll my twitter feed than keep clicking Next Page.
Is it me or is it impossible to scroll that page in Safari?
Gee. Google code not working on non-google browsers. What a surprise. Speaking as a firefox user, I'm lucky if google docs even loads, let alone works properly. Yet a another example of google talking out of their ass about "supporting web standards"
Not joking: http://www.creativebloq.com/web-design/parallax-scrolling-11...
Earlier quoted context omitted.
Gee. Google code not working on non-google browsers. What a surprise. Speaking as a firefox user, I'm lucky if google docs even loads, let alone works properly. Yet a another example of google talking out of their ass about "supporting web standards"
They are apparently aware of it at least. https://news.ycombinator.com/item?id=11882964
For a React implementation, look no further than react-virtualized ( https://github.com/bvaughn/react-virtualized ). Performant, great featureset, and one of the most accessible, responsive maintainers I've ever seen in an open source project.