Unbind scroll event when reinstantiated

[pedantic-git]

There was a bug when elem.infinitePages() was called on a second element - the window.scroll was not unbound and so links generated still came from the old context/container.

In most cases, this one-line change fixes the turbolinks issues people are experiencing in #5. Just remember to reinstantiate infinitePages whenever turbolinks changes the page. For example (in my app):

ready = ->
  # Configure infinite table
  $('.infinite-table').infinitePages
    loading: ->
      $(this).text('Loading next page...')
    error: ->
      $(this).button('There was an error, please try again')
$(document).ready(ready)
$(document).on('turbolinks:load', ready)

[LannyBose]

I inlined this one change locally and it fixed my issues with the following sequence (while using Turbolinks 5):

• Visit an infinite scroller
• Scroll once (but not to completion)
• Navigate forward
• Navigate back

...which previously had resulted in shenanigans. 👍