Skip to content

SideNav [opened] property bound not working correctly when bound to an observable #6985

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

Closed
stocksr opened this issue Sep 11, 2017 · 5 comments · Fixed by #6810
Closed

SideNav [opened] property bound not working correctly when bound to an observable #6985

stocksr opened this issue Sep 11, 2017 · 5 comments · Fixed by #6810

Comments

@stocksr
Copy link

stocksr commented Sep 11, 2017

Bug, feature request, or proposal:

Bug: When you bind the opened property of a sidenav to an Observable and that Observable changes again while the animation is running the sidebar ignores the change.

What is the expected behavior?

The sidebar should always end up in a state that matches the observable.

What is the current behavior?

The side bar ignores changes while it is processing the previous one.

What are the steps to reproduce?

In this plunker: http://plnkr.co/edit/DSBJmIPJzjhoeg2rGx2z?p=preview
If you press the bounce button the sidebar should end up in the open state.
alternatively if you press the open and close buttons in rapid succession you can also end up with the wrong state.

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Material beta 10 (This worked in beta 8)

@willshowell
Copy link
Contributor

See #6376

@Nodarii
Copy link

Nodarii commented Sep 11, 2017

@stocksr ,

I face such behavior, but it is not connected to the observable. Component can not be closed until it is fully shown (I mean animation is done)

@stocksr
Copy link
Author

stocksr commented Sep 11, 2017

thanks - I even looked for this issue before reporting - but I was looking for it under SideNav not drawer.
PR #6810 looks like it will fix it, any idea when that will land?

@willshowell
Copy link
Contributor

@stocksr since it's marked as ready, probably this week. The team typically merges about twice a week, but there are often presubmit failures or merge conflicts that postpone it to the next round.

@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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants