-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[sidenav] can't close until opening animation is complete #6376
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
Comments
@crisbeto seems like this may have been a regression from one of your PRs |
@crisbeto are you aware of any open issues in core for #5743 and #4932? If I understand correctly, the current behavior is necessary until those are sorted out? Further, could you explain this note? Is that to say that the promise return value will become obsolete, but is there to match the before-animations behavior? |
Yes, the previous approach was passing promises around to coordinate the animation, but I removed all of them in #4959 since they weren't necessary anymore. The ones for |
Got some time to look into this. It seems like #5743 isn't an issue for the sidenav. I'll remove the |
Fixes not being able to toggle a drawer while it is mid-animation. Fixes angular#6376.
Fixes not being able to toggle a drawer while it is mid-animation. Fixes angular#6376.
Fixes not being able to toggle a drawer while it is mid-animation. Fixes angular#6376.
Fixes not being able to toggle a drawer while it is mid-animation. Fixes angular#6376.
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. |
Bug, feature request, or proposal:
Regression
Expected
Sidenav can still be closed while animating open
Current
Sidenav must wait until animation is complete to trigger new actions
Reproduction
Working with beta.8: https://plnkr.co/edit/Ucv13OC4Zsl55CXRANK3?p=preview
Failing with latest: https://plnkr.co/edit/pCWLJ2ThQrKgGXI2Q9cn?p=preview
Other
Presumably due to #4959 or #6189
The text was updated successfully, but these errors were encountered: