_______________ | header | | | | buffered | | images up | |-------------| | | | Viewport | | | | | |-------------| | buffered | | images down | | | | | ---------------
Is this somehow technically very difficult or would this screw with usability in some way that would be unintuitive?
We do the masonry layout from left to right. This means we start filling out each row from the left and can leave space on the right of the last row of a page so the next page can begin filling in the remainder of that row before starting a new one. To do this the opposite way if we're "backfilling" photos seems like it could be significantly more complex.
In essence when scrolling "up" we'd have to reverse the alignment and fill photos in from right to left. This alone makes my head hurt to think about.
But aside from our implementation I think a bidirectional infinite scroll really is the solution to work towards. It would feel much more natural that way.
Then it is just taking a list of images, and moving the "view" forward or backward on that list, right?
Totally agreed there are other more issues to tackle than scroll position. scrollFrame was a useful little hack born out of a need to solve a glaring problem on a deadline :) I wanted something that we could drop on any existing page with minimal integration effort and so far it's proven pretty useful in that regard.
It's a problem we recently tackled on our infinite scrolling page. Combining modals, pushState (on scroll) and waypoints I think we've solved the the most important problems we introduced with infinite scroll on our gallery page. Here's an example [1] and a blog post about the attention we paid to detail [2].
[1] https://current.trovebox.com/photos/page-1/list
[2] https://medium.com/p/636c0ae6e3b1