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

Animation query parameter does not work properly #17632

Closed
Ledzz opened this issue Jun 20, 2017 · 4 comments · Fixed by #17737
Closed

Animation query parameter does not work properly #17632

Ledzz opened this issue Jun 20, 2017 · 4 comments · Fixed by #17737
Assignees

Comments

@Ledzz
Copy link

Ledzz commented Jun 20, 2017

I'm submitting a ...


[ ] Regression (behavior that used to work and stopped working in a new release)
[x] Bug report 
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

All child query(':enter') transitions work

Expected behavior

Only first query(':enter') transition works

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/qaJpj4Maf0QobAv8bXe6?p=preview
Click Toggle button. All Bar elements should animate, but this doesn't happen.

What is the motivation / use case for changing the behavior?

Please tell us about your environment


Angular version: 4.2.3


Browser:
- [x] Chrome (desktop) version 58.0.3029.110 (64-bit)
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX 
- Platform: 

Others:

@Ledzz
Copy link
Author

Ledzz commented Jun 20, 2017

I finally managed to make some workaround for this. You can use animateChild and another animation.

trigger('listAnimation', [
	transition('* => *', [
		query('@slideIn', [
			stagger(30, [
				animateChild()
			]),
		], { optional: true })
	]),
])

Here's a plunkr: http://plnkr.co/edit/QWgiE4tYLN3O2Tnx1E7j?p=preview

@matsko matsko self-assigned this Jun 23, 2017
@matsko
Copy link
Contributor

matsko commented Jun 23, 2017

I believe this fixes the issue: #17534

@matsko
Copy link
Contributor

matsko commented Jun 23, 2017

Not sure just yet. I will get to this once that's in.

matsko added a commit to matsko/angular that referenced this issue Jun 23, 2017
matsko added a commit to matsko/angular that referenced this issue Jun 24, 2017
matsko added a commit to matsko/angular that referenced this issue Jun 27, 2017
matsko added a commit to matsko/angular that referenced this issue Jun 27, 2017
matsko added a commit to matsko/angular that referenced this issue Jun 28, 2017
matsko added a commit that referenced this issue Jun 29, 2017
matsko added a commit to matsko/angular that referenced this issue Jun 29, 2017
matsko added a commit that referenced this issue Jun 30, 2017
asnowwolf pushed a commit to asnowwolf/angular that referenced this issue Aug 11, 2017
juleskremer pushed a commit to juleskremer/angular that referenced this issue Aug 28, 2017
@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 Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants