One 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
Google’s suggestion for a better infinite scroll?
31–40 of 168 posts
Re: Google’s suggestion for a better infinite scroll?
#32It still jumps around if you hold and drag the scrollbar - always my complaint with these.
This should be fixed by the browser. If mouse is hold-clicked on scrollbar and the height of the document changes. the position of the mouse should change as well.
What's the problem with that?
Re: Google’s suggestion for a better infinite scroll?
#33One 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
There's a link to the footer, and the footer links are in a fixed footer that is always visible. Not super-pretty but I think infinite scroll just means no footer.
Re: Google’s suggestion for a better infinite scroll?
#34It still jumps around if you hold and drag the scrollbar - always my complaint with these.
This should be fixed by the browser. If mouse is hold-clicked on scrollbar and the height of the document changes. the position of the mouse should change as well. What's the problem with that?
I don't think the browser is technically able to move the mouse cursor, I imagine that happens at the OS level. Anyone have a counterexample?
Re: Google’s suggestion for a better infinite scroll?
#35Reminds me how much I dislike infinite scrolling.
Re: Google’s suggestion for a better infinite scroll?
#36Doesn't this still effectively break the back button or at least the users view of the back button? To the user although there are visual hints, he/she hasn't left the page. Scrolling down the page however creates multiple history entries.
I was mistaken. I must have clicked through to a page.
Re: Google’s suggestion for a better infinite scroll?
#37Earlier quoted context omitted.
This should be fixed by the browser. If mouse is hold-clicked on scrollbar and the height of the document changes. the position of the mouse should change as well. What's the problem with that?
I don't think the browser is technically able to move the mouse cursor, I imagine that happens at the OS level. Anyone have a counterexample?
The OS has APIs that applications like the browser can use for that, e.g.:
Win32: http://msdn.microsoft.com/en-us/library/windows/desktop/ms64...
Re: Google’s suggestion for a better infinite scroll?
#38I'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.
Re: Google’s suggestion for a better infinite scroll?
#39Love 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.
Re: Google’s suggestion for a better infinite scroll?
#40I really liked Discourse's approach to infinite scrolling[1], it updates the URL as you go with the History API's replaceState() function so you can safely navigate away from the page without losing your position. [1]: http://eviltrout.com/2013/02/16/infinite-scrolling-that-work...
Also, visually, the up page# down could be shown on the right hand side. [http://try.discourse.org/t/discussion-happens-so-much/127/98] and with a bigger font. that's more clear. putting it in the bottom is hard to read.