We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Bug
When the mode input is dynamically updated from over to side, the backdrop should be removed if it is currently present on the screen.
When the mode input is dynamically updated from over to side, the backdrop is not removed if it is currently present on the screen.
Providing a Plunker (or similar) is the best way to get the team to see your issue. Plunker template: https://goo.gl/DlHd6U
This should be considered a bug fix.
Angular 4.3.6 Material 2.0.0-beta.10 OS X 10.11.6 TS 2.3.4 Chrome 60.0.3112.113
The text was updated successfully, but these errors were encountered:
See #6271
Sorry, something went wrong.
Closing as duplicate of #6271
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.
No branches or pull requests
Bug, feature request, or proposal:
Bug
What is the expected behavior?
When the mode input is dynamically updated from over to side, the backdrop should be removed if it is currently present on the screen.
What is the current behavior?
When the mode input is dynamically updated from over to side, the backdrop is not removed if it is currently present on the screen.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
This should be considered a bug fix.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.3.6
Material 2.0.0-beta.10
OS X 10.11.6
TS 2.3.4
Chrome 60.0.3112.113
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: