Closed allolex closed 5 years ago
Using the current implementation it should not have to be refreshed. As taken from the Turbolinks docs:
turbolinks:render fires after Turbolinks renders the page. This event fires twice during an application visit to a cached location: once after rendering the cached version, and again after rendering the fresh version.
link
Please provide a working example of the problem. Your suggested solution would not work if javascript is asynced or turbolinks is disabled.
turbolinks:render
I don't think this is the right solution.
The grid column filter requires the page to be refreshed on a Rails 4.2.8 project.
Loading Turbolinks via the
turbolinks:load
handler fixes this problem.https://github.com/turbolinks/turbolinks#running-javascript-when-a-page-loads