Skip to content
New issue

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

dialog error Failed to execute 'animate' on 'Element': Partial keyframes are not supported. #5019

Closed
ghost opened this issue Jun 8, 2017 · 1 comment · Fixed by #5020
Closed
Assignees
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@ghost
Copy link

ghost commented Jun 8, 2017

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

@crisbeto crisbeto self-assigned this Jun 8, 2017
@crisbeto crisbeto added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful has pr labels Jun 8, 2017
crisbeto added a commit to crisbeto/material2 that referenced this issue Jun 8, 2017
Fixes an error being thrown by the dialog animations. It looks like it was triggered as a result of the changes from 28d2ddd.

Fixes angular#5019.
andrewseguin pushed a commit that referenced this issue Jun 8, 2017
Fixes an error being thrown by the dialog animations. It looks like it was triggered as a result of the changes from 28d2ddd.

Fixes #5019.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant