-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Waves to v0.7.5 #5472
Comments
We are currently using a modified waves.js version but we can probably add the init method and migrate the affected lines in Materialize. |
Why do you need to call displayEffect() multiple times? As long as the element has waves-effect it should still be able to trigger the waves effect without having to call displayEffect() |
Niels-Be
added a commit
to Niels-Be/materialize
that referenced
this issue
Aug 5, 2018
This is 99% origignal Waves.js code. The only thing added was the initialisation on dom load in line 31.
Niels-Be
added a commit
to Niels-Be/materialize
that referenced
this issue
Aug 5, 2018
This is 99% original Waves.js code. The only thing added was the initialization on DomLoad in line 31.
Niels-Be
added a commit
to Niels-Be/materialize
that referenced
this issue
Aug 10, 2020
This is 99% original Waves.js code. The only thing added was the initialization on DomLoad in line 31.
JayDijkstra
pushed a commit
to JayDijkstra/materialize
that referenced
this issue
Mar 7, 2021
This is 99% original Waves.js code. The only thing added was the initialization on DomLoad in line 31.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was looking for a more performant solution for my Angular project besides calling
Waves.displayEffect()
each time a new component loads and saw that there is nowWaves.init()
which seems to be a one-time call.https://github.com/fians/Waves/blob/master/src/js/waves.js
The text was updated successfully, but these errors were encountered: