Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add a Materialize.init() function
See original GitHub issueTurbolinks is ruby gem massively used by Ruby on Rails applications. It intercepts each get request, fetches the content and swaps is without doing the full page reload.
Since document ready is not triggered after the content is dynamically swapped, materialize js is not initialized.
Since turbolinks offer custom events, problem could be easily solved if there is a nice and simple way to dynamically initialize js modules. Something like Materialize.init(). It can then be internally called on document ready, but would further allow developers to manually initialize them whenever needed.
I’m sure that turbolinks are just one example and that there are many more cases where this issue arises.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The event listener should also fire for dynamically added elements.
Added to the feature request board