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
fix(animations): always fire inner trigger callbacks even if blocked by parent animations #19753
Conversation
You can preview f50f537 at https://pr19753-f50f537.ngbuilds.io/. |
syncPlayerEvents(player: AnimationPlayer) { | ||
const p = this._player as any; | ||
if (p.triggerCallback) { | ||
player.onStart(() => p.triggerCallback !('start')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove !
f50f537
to
bc92c79
Compare
You can preview bc92c79 at https://pr19753-bc92c79.ngbuilds.io/. |
…blocked by parent animations (angular#19753)" This reverts commit 5a9ed2d.
You can preview bc92c79 at https://pr19753-bc92c79.ngbuilds.io/. |
This broke a test in G3. |
bc92c79
to
9bcd709
Compare
You can preview c260a65 at https://pr19753-c260a65.ngbuilds.io/. |
…by parent animations Closes angular#19100
c260a65
to
7cdd829
Compare
You can preview 7cdd829 at https://pr19753-7cdd829.ngbuilds.io/. |
@mhevery This PR seems to have been reverted but it is listed in the current changelog for the 5.1.0-beta1 release. Am I missing something? |
…by parent animations (angular#19753) Closes angular#19100 PR Close angular#19753
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Closes #19100