dialog error Failed to execute 'animate' on 'Element': Partial keyframes are not supported. #5019
Labels
P1
Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Bug, feature request, or proposal:
bug
What is the expected behavior?
dialog open correctly
What is the current behavior?
this.dialogRef = this.dialog.open(addDialog, this.config);
open error:
:56960/node_modules/@angular/core/bundles/core.umd.js:1091 ERROR DOMException: Failed to execute 'animate' on 'Element': Partial keyframes are not supported.
at WebAnimationsPlayer._triggerWebAnimation (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:2314:35)
at WebAnimationsPlayer.init (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:2297:29)
at InjectableAnimationEngine.DomAnimationEngine._queuePlayer (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1589:16)
at InjectableAnimationEngine.DomAnimationEngine.animateTransition (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1504:14)
at InjectableAnimationEngine.DomAnimationEngine.setProperty (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1375:18)
at AnimationRenderer.setProperty (http://localhost:56960/node_modules/@angular/platform-browser/bundles/platform-browser-animations.umd.js:234:26)
at setElementProperty (http://localhost:56960/node_modules/@angular/core/bundles/core.umd.js:9586:19)
at checkAndUpdateElementValue (http://localhost:56960/node_modules/@angular/core/bundles/core.umd.js:9505:13)
at checkAndUpdateElementInline (http://localhost:56960/node_modules/@angular/core/bundles/core.umd.js:9443:24)
at checkAndUpdateNodeInline (http://localhost:56960/node_modules/@angular/core/bundles/core.umd.js:12238:23)
Unhandled Promise rejection: Cannot read property 'play' of undefined ; Zone: ; Task: Promise.then ; Value: TypeError: Cannot read property 'play' of undefined
at WebAnimationsPlayer.play (:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:2349)
at _loop_2 (:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1627)
at InjectableAnimationEngine.DomAnimationEngine._flushQueuedAnimations (:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1632)
at InjectableAnimationEngine.DomAnimationEngine.flush (:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1653)
at eval (:56960/node_modules/@angular/platform-browser/bundles/platform-browser-animations.umd.js:271)
at ZoneDelegate.invoke (zone.js:391)
at Zone.run (zone.js:141)
at zone.js:817
at ZoneDelegate.invokeTask (zone.js:424)
at Zone.runTask (zone.js:191) TypeError: Cannot read property 'play' of undefined
at WebAnimationsPlayer.play (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:2349:21)
at _loop_2 (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1627:24)
at InjectableAnimationEngine.DomAnimationEngine._flushQueuedAnimations (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1632:27)
at InjectableAnimationEngine.DomAnimationEngine.flush (http://localhost:56960/node_modules/@angular/animations/bundles/animations-browser.umd.js:1653:14)
at eval (http://localhost:56960/node_modules/@angular/platform-browser/bundles/platform-browser-animations.umd.js:271:35)
at ZoneDelegate.invoke (http://localhost:56960/node_modules/zone.js/dist/zone.js:391:26)
at Zone.run (http://localhost:56960/node_modules/zone.js/dist/zone.js:141:43)
at http://localhost:56960/node_modules/zone.js/dist/zone.js:817:57
at ZoneDelegate.invokeTask (http://localhost:56960/node_modules/zone.js/dist/zone.js:424:31)
at Zone.runTask (http://localhost:56960/node_modules/zone.js/dist/zone.js:191:47)
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
material demo demo-app\dialog\dialog-demo.html
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
[email protected]
Is there anything else we should know?
with [email protected] update at 2017.6.6 dialog.open work well
The text was updated successfully, but these errors were encountered: