Skip to content

fix(stepper): emitting the animationDone event twice on some browsers - #13608

Merged
josephperrott merged 1 commit into
angular:masterfrom
crisbeto:stepper-duplicate-animation-events
Oct 19, 2018
Merged

fix(stepper): emitting the animationDone event twice on some browsers#13608
josephperrott merged 1 commit into
angular:masterfrom
crisbeto:stepper-duplicate-animation-events

Conversation

@crisbeto

Copy link
Copy Markdown
Member

Along the same lines as #13600 and #13587. The animationDone will be emitted twice in a row for some browsers due to a bug in @angular/animations.

Along the same lines as angular#13600 and angular#13587. The `animationDone` will be emitted twice in a row for some browsers due to a bug in `@angular/animations`.
@crisbetocrisbeto added the target: patch This PR is targeted for the next patch release label Oct 14, 2018
@googlebotgooglebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 14, 2018
@mmalerbammalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 18, 2018
@josephperrott
josephperrott merged commit 3ef933a into angular:masterOct 19, 2018
josephperrott pushed a commit that referenced this pull request Oct 19, 2018
…#13608)
Along the same lines as #13600 and #13587. The `animationDone` will be emitted twice in a row for some browsers due to a bug in `@angular/animations`.
josephperrott pushed a commit that referenced this pull request Oct 19, 2018
…#13608)
Along the same lines as #13600 and #13587. The `animationDone` will be emitted twice in a row for some browsers due to a bug in `@angular/animations`.
@angular-automatic-lock-bot

Copy link
Copy Markdown

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-botangular-automatic-lock-botBot locked and limited conversation to collaborators Sep 9, 2019
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: mergeThe PR is ready for merge by the caretakercla: yesPR author has agreed to Google's Contributor License Agreementtarget: patchThis PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@crisbeto@mmalerba@googlebot@josephperrott