"Failed to execute 'animate' ... no function was found that matched" after 2.2.0
See original GitHub issueI’m testing this on a fairly new Android 5.1.1 browser with a WebView of 44.0.2403.133 and using this code:
this.element.animate({
opacity: [0, 1]
}, {
duration: 300,
fill: 'forwards'
});
That code fails on that environment with Uncaught TypeError: Failed to execute 'animate' on 'Element': The provided value is not of type '(EffectModel or sequence<Dictionary>)'.
I did test this code on IE11, Chrome, Firefox and Safari (all latest versions) though and it seems to work fine.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
"Failed to execute 'animate' ... no function was found ... - GitHub
I'm testing this on a fairly new Android 5.1.1 browser with a WebView of 44.0.2403.133 and using this code: this.element.animate({ opacity: ...
Read more >anime.js animation not working, (the animation doesn't get ...
Your element does not exist when you execute the document.querySelector statement. Wrap your code in a load event listener.
Read more >.animate() | jQuery API Documentation
A Boolean indicating whether to place the animation in the effects queue. If false, the animation will begin immediately. As of jQuery 1.7,...
Read more >Fixed issues in Animate release - Adobe Support
[macOS] Missing workspaces, files error after launching the application with fresh preferences after macOS 12.3.1 update.
Read more >Cloud Composer release notes | Google Cloud
Cloud Composer now generates an error message if an environment label matches internal environment labels used by Cloud Composer. (Available without upgrading) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Just released 2.2.1 with a fix for this issue. Thank you for the reports, please let me know if there are any further issues.
Thanks @alancutter for your detail clarification. This really helps!