-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
SnackBar does not close zone when dismissed #4859
Comments
We should do |
Good point, @jelbourn. That complicates the timeout handling: Which way do you prefer? |
I would just move the setTimeout call into the snackbar ref in a function like |
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
When a duration is passed to MdSnackBar.prototype.openFromComponent(), a timeout is created. This timeout is now cleared when dismissing the snackbar. Fixes angular#4859
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:
SnackBar should close duration zone when dismissed, so protractor is not blocked.
What is the expected behavior?
When calling MdSnackBarRef.prototype.dismiss(), the timeout reference by setTimeout should be cleared to close the angular zone.
What is the current behavior?
The zone stays open for the duration of the timeout.
What are the steps to reproduce?
Plunker (watch the zone state)
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/[email protected]
The text was updated successfully, but these errors were encountered: