craigspaeth

This specific issue with FF should be fixed now. Check http://artsy.github.io/scroll-frame/demo.html to see if it works on your end. Thanks for checking it out :)

Yeah I noticed that too :( Logged here: https://github.com/artsy/scroll-frame/issues/10. Hopefully there's a way around this.

I think I've fixed the problem. I had to move the url to work around the Github cache so the new demo can be found here: http://artsy.github.io/scroll-frame/demo.html

Please let me know if you're still getting this problem. Thanks for reporting this!

I have a repro thanks to github.com/ilyakava! Looks like installing the Buffer chrome extension can expose this bug. https://github.com/artsy/scroll-frame/issues/11 Probably something weird I'm doing with pushState.

Tell me about it. If you've ever used iScroll (amazing library btw https://github.com/cubiq/iscroll) to get iPad scrolling support you'll see how deep the rabbit hole goes. I initially used it for 2013.artsy.net (source code: https://github.com/artsy/artsy-2013) and had to eventually decide to toggle it on only for iPad b/c there were too many edge cases in the browser.

But I digress. Thanks for pointing this out, hopefully we'll eventually smooth over the quirks to a reasonable degree. Logged the bug for now: https://github.com/artsy/scroll-frame/issues/12

That's a fair point. I think there are arguments for both pagination and infinite scroll and one is not necessarily better than the other. Jeff Atwood has an interesting post on this http://blog.codinghorror.com/the-end-of-pagination/ where I think he makes a good point about "[...] once you have thousands of items to paginate, who the heck is visiting page 964 of 3810?". On the other hand infinite scroll has a slew of quirks with it too, so there are arguments both ways.

We use a separate mobile website for almost all of our web views so I have yet to integrate it on mobile. I assume one would have to be more careful about the performance of embedding an iframe in that context.

Ahh, thanks for report. Looks like I have a little way to go to ensure cross-modern-browser support. I noticed some odd things going on in Firefox. What browser/version are you using?

You definitely should get on that :) That approach has been in the back of my mind for a while and I'd love to leverage a library for it.

Very cool! Can't believe I hadn't come across this blog post earlier—I'll definitely be reading.

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.

Thanks for checking it out! To the footer question—I think you just caught a bug :) Logging it!

We usually try to remove the footer e.g. on our posts page https://artsy.net/posts/featured

Odd, what link did you click to get to that url? If you follow this link http://artsy.github.io/scroll-frame/ it should show a bunch of cute little kittens infinitely adding themselves to your page: http://cl.ly/image/1d2z2h0G3Z1U

Thanks for checking this out! As you guessed it going down further than one page can cause some state headaches such as navigating into another infinite scroll view and stacking iframes inside of iframes, so I decided to cut it off after the first. I'm trying to log some caveats here: https://github.com/artsy/scroll-frame#caveats

To the data tracking question: We conducted usability tests on our fair pages (artsy.net/the-armory-show) that brought this issue to the forefront. In these tests users consistently would open artwork pages expecting not to lose their place in infinite scroll. However, we haven't dived into our data yet to discover the full range of ways in which people navigate infinite scroll lists.

Yeah sorry about that. I removed Vertebrae and Sentry because they were over-engineered and weren't that useful. Vertebrae did some things to help with relations and identity maps in Backbone but there are already better solutions out there now.

e.g.

https://github.com/PaulUithol/Backbone-relational

https://supportbee.com/devblog/2011/11/25/identity-map-for- backbone-js-models/

https://news.ycombinator.com/item?id=3276990 (Discussion on jashkenas pattern for a solution to identity maps)

https://gist.github.com/3057320