> On Jul 28, 2016, at 4:37 AM, Johnny Stewart <[email protected]> wrote:
> 
> I'd start looking around there, try disabling turbolinks and see if that 
> makes a difference..

But don't leave it off -- use this as a test to see if that's the problem, and 
then edit your script to change the event it observes from 'ready' to 
'page:change'. The latter is added to the page load sequence by Turbolinks, and 
it is a catch-all -- it fires on a full reload and a turbolinks page replace -- 
so you only have to listen to one event to get all types of page "load".

Walter

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/DBA62B62-9430-4EE7-9D90-10D7031D388F%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to