21–30 of 30 posts
Earlier quoted context omitted.
Depends, infinite scrolling can be and has been done right [0], but it's really not the focus of the feature -- it's a product. [0] http://warpspire.com/experiments/history-api/
Maybe I just haven't seen it done right - do you have some example links?
The next 5-10 years are going to be interesting.
Earlier quoted context omitted.
Having a linkable infinite scroll is only solving one of the issues in infinite scroll. Have you ever tried to click the links in Facebook below your news feed? Why is it that everyone who implements automatic infinite scroll shoves it into a context where there's stuff beneath it on the page, making that content completely inaccessible?
No, because FB puts the same links and content under the right-hand side. Can you enumerate the issues that need to be addressed? I have ready of research on the lack-luster implementations (eg. Twitter) that many assume is the status quo.
I can't be the only one that absolutely despises infinitely scrolling lists, right?
I can't be the only one that absolutely despises infinitely scrolling lists, right?
Badly implemented ones (which is 97% of those on web sites) on the other hand...
Earlier quoted context omitted.
No, because FB puts the same links and content under the right-hand side. Can you enumerate the issues that need to be addressed? I have ready of research on the lack-luster implementations (eg. Twitter) that many assume is the status quo.
My biggest problem is how to get back to where I was. I was reading a funny tumblr on my phone and got to the point where the page was incredibly slow, so I wanted to start reading again from where I currently was in the page... how do I do that?
I can't be the only one that absolutely despises infinitely scrolling lists, right?
All other cases of finite lists shouldn't use infinite scrolling. It breaks jumping back to a specific position and the length is not predictable.
I can't be the only one that absolutely despises infinitely scrolling lists, right?
I can't tell if this would help rendering large lists of dom elements that are loaded all at once... eg what things like infinity.js, ember tables, etc do. I wish there was a UITableView for the web that was more native than any of those solutions.
Mozilla's XUL had a native treeview element, and I remember it being horrible to work with. https://developer.mozilla.org/en-US/docs/XUL/tree