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
Hej and thank you very very much for this great plugin. We love it!
Now here's a tiny little feature request that would make the plugin even better, as we think.
Context:
We're setting the loading element in DOM already to have a loading animation as early as possible. This works and looks really good.
Problem:
When animsition calls addLoading it doesn't check if an element with the loading class already exists on the page. So it's being added twice, which looks bad and doesn't make a lot of sense
Proposed solution:
in addLoading check if an element with the options.loadingClass already exists on the page and only add it, if it doesn't.
We've patched the plugin this way and it works wonderful, so we'd guess this might also be helpful for other users because the loading element doesn't make sense to be duplicated on the same page, as we think.
Proposed solution:
in addLoading check if an element with the options.loadingClass already exists on the page and only add it, if it doesn't
I observed this tinny bug may times for myself, but thanks to your little fix loaders are now started properly. Tested on several instances with various web apps and it works everywhere.
Hej and thank you very very much for this great plugin. We love it!
Now here's a tiny little feature request that would make the plugin even better, as we think.
Context:
We're setting the loading element in DOM already to have a loading animation as early as possible. This works and looks really good.
Problem:
When animsition calls addLoading it doesn't check if an element with the loading class already exists on the page. So it's being added twice, which looks bad and doesn't make a lot of sense
Proposed solution:
in addLoading check if an element with the options.loadingClass already exists on the page and only add it, if it doesn't.
We've patched the plugin this way and it works wonderful, so we'd guess this might also be helpful for other users because the loading element doesn't make sense to be duplicated on the same page, as we think.
So here's the simple and tested code:
The text was updated successfully, but these errors were encountered: