We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Linked to my previous issue report, i managed to style my button to overpass bootstrap css classes.
But, i discovered another thing.
After having finished to run, you script "leaves" some css style attached to the element:
outline: 0px; box-shadow: rgba(232, 163, 22, 0) 0px 0px 13px; outline-offset: 20px;
These lines overpass my own design and make my buttons disappear (by removing offset and shadow).
So my question is :Is there any way for pulsate to LEAVE (or put back) the target element at its initial css state?
I don't know if it can "memorize" the css of my element and then put it back after pulsate have done its business.
The text was updated successfully, but these errors were encountered:
After destroying the pulsate element, you can remove the style as well. $('.myclass').pulsate('destroy'); $('.myclass').removeAttr('style');
This works good, unless you are using inline styles in the element.
Sorry, something went wrong.
No branches or pull requests
Linked to my previous issue report, i managed to style my button to overpass bootstrap css classes.
But, i discovered another thing.
After having finished to run, you script "leaves" some css style attached to the element:
These lines overpass my own design and make my buttons disappear (by removing offset and shadow).
So my question is :Is there any way for pulsate to LEAVE (or put back) the target element at its initial css state?
I don't know if it can "memorize" the css of my element and then put it back after pulsate have done its business.
The text was updated successfully, but these errors were encountered: