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
I have come up with a simple alternative strategy that allows Sentinel to not conflict with previously defined animations: Just add a data attribute after the event fires and then make the animation use a negative attribute selector.
I don't think it's perfect as you will probably have a flicker as the JS will take time to run but maybe it's better?
The text was updated successfully, but these errors were encountered:
danielbodart
changed the title
Alternative strategy for not conflicting with animation names...
Alternative strategy for not conflicting with previous animations...
Sep 27, 2020
I have come up with a simple alternative strategy that allows Sentinel to not conflict with previously defined animations: Just add a data attribute after the event fires and then make the animation use a negative attribute selector.
CSS
Javascript
Link to a CodePen example: https://codepen.io/danielbodart/pen/MWyxNQY
I don't think it's perfect as you will probably have a flicker as the JS will take time to run but maybe it's better?
The text was updated successfully, but these errors were encountered: