You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I would like to share a problem and solution I came across this morning whilst integrating mdbootstrap with my application. My stack is routed with the angular ui-router component and I was noticing that none of my buttons were getting the waves-effect ripple animation.
After some debugging I found this to be due to when the Waves are initialized with the displayEffect() function.
With the angular ui-router component, the DOMContentLoaded method is fired prematurely to an application being fully loaded and instead I found hooking into the ui-router API event $viewContentLoaded to manually call the event, initialized the ripples properly.
My next foreseeable problem will be with modals when they are initialized, or any other DOM manipulation that doesn't come from the ui-router skipping the $viewContentLoaded event.
Will keep post updated.
The text was updated successfully, but these errors were encountered:
Hi,
I would like to share a problem and solution I came across this morning
whilst integrating mdbootstrap with my application. My stack is routed with
the angular ui-router component and I was noticing that none of my buttons
were getting the waves-effect ripple animation.
After some debugging I found this to be due to when the Waves are
initialized with the displayEffect() function.
document.addEventListener('DOMContentLoaded', function () {
Waves.displayEffect();
}, false);
With the angular ui-router component, the DOMContentLoaded method is
fired prematurely to an application being fully loaded and instead I found
hooking into the ui-router API event $viewContentLoaded to manually call
the event, initialized the ripples properly.
My next foreseeable problem will be with modals when they are initialized,
or any other DOM manipulation that doesn't come from the ui-router skipping
the $viewContentLoaded event.
Will keep post updated.
Please note this is for version 3.4.0.
Hi,
I would like to share a problem and solution I came across this morning whilst integrating mdbootstrap with my application. My stack is routed with the angular ui-router component and I was noticing that none of my buttons were getting the waves-effect ripple animation.
After some debugging I found this to be due to when the Waves are initialized with the
displayEffect()
function.With the angular ui-router component, the
DOMContentLoaded
method is fired prematurely to an application being fully loaded and instead I found hooking into the ui-router API event$viewContentLoaded
to manually call the event, initialized the ripples properly.My next foreseeable problem will be with modals when they are initialized, or any other DOM manipulation that doesn't come from the ui-router skipping the $viewContentLoaded event.
Will keep post updated.
The text was updated successfully, but these errors were encountered: