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
{{ message }}
This repository was archived by the owner on Oct 30, 2024. It is now read-only.
On Chrome and Firefox, the first filter a user chooses works fine but any subsequent filters that are chosen do not work and produces the following error in the console.
MixItUp] WARNING: An operation was requested but the MixItUp instance was busy. The operation was rejected because the queue is full or queuing is disabled.
It appears the animation never really finishes and causes the subsequent filter events to never get triggered. This issue has been brought up once before in issue #278. A solution proposed in that issue thread was to decrease the animation duration. I tried that but it did not work. The other solution mentioned would be to increase the throttle duration to a greater value than your mixer animation duration. This did not work. The last solution i tried out was increasing the queueLimit but that did not work either. The only band-aid fix that made the filters work again was to disable the animations completely, which isn't a great fix for UX reasons.
The text was updated successfully, but these errors were encountered:
We add the same issue on a project with lot of items. My solution is to replace the MixItUp animations by CSS animations, all is explain in this article (in French), but the code will remain the same 😉
The error can be seen here: https://elearning.scranton.edu/programs/
On Chrome and Firefox, the first filter a user chooses works fine but any subsequent filters that are chosen do not work and produces the following error in the console.
MixItUp] WARNING: An operation was requested but the MixItUp instance was busy. The operation was rejected because the queue is full or queuing is disabled.
It appears the animation never really finishes and causes the subsequent filter events to never get triggered. This issue has been brought up once before in issue #278. A solution proposed in that issue thread was to decrease the animation duration. I tried that but it did not work. The other solution mentioned would be to increase the throttle duration to a greater value than your mixer animation duration. This did not work. The last solution i tried out was increasing the
queueLimit
but that did not work either. The only band-aid fix that made the filters work again was to disable the animations completely, which isn't a great fix for UX reasons.The text was updated successfully, but these errors were encountered: