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.

Sign up for GitHub

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

Jump to bottom

MdSnackBar from Component auto-close, won't open #7063

Closed
SaturnTeam opened this issue Sep 14, 2017 · 1 comment · Fixed by #7086
Closed

MdSnackBar from Component auto-close, won't open #7063

SaturnTeam opened this issue Sep 14, 2017 · 1 comment · Fixed by #7086
Assignees
@crisbeto

Comments

@SaturnTeam
Copy link

Bug, feature request, or proposal:

Bug

What is the expected behavior?

Opening snackbar from component without set duration and already opened from same component snackbar will appear.

What is the current behavior?

Snackbar auto close by it self, if there is no duration option

What are the steps to reproduce?

  1. open bar from component
  2. try to open it again
    You will see, snackbar will close and never showed again. If you have animations module, you can see how new snackbar starts to appear, and then closes.
    If you set up duration in config, everything will be fine.
    https://plnkr.co/edit/zuumORaByIHLHBKKHLse?p=preview
@crisbeto crisbeto self-assigned this Sep 14, 2017
crisbeto added a commit to crisbeto/material2 that referenced this issue Sep 14, 2017
@crisbeto
fix(snack-bar): subsequent snack bars not opening; animation issues
6ee2c34 
* Fixes subsequent snack bars not showing up if they are opened while another snack bar is open. This was due to the latter snack bar getting closed immediately, because one of the animation events coming in is `void->void`.
* Simplifies the logic for determining the animation state. Using the getter ended up passing returning an invalid state in some cases (e.g. `undefined-top` or `undefined-bottom`).

Fixes angular#7063.
@crisbeto crisbeto mentioned this issue Sep 14, 2017
Merged
andrewseguin pushed a commit that referenced this issue Sep 29, 2017
@crisbeto @andrewseguin
fix(snack-bar): subsequent snack bars not opening; animation issues (#…
8e77261 
…7086)

* Fixes subsequent snack bars not showing up if they are opened while another snack bar is open. This was due to the latter snack bar getting closed immediately, because one of the animation events coming in is `void->void`.
* Simplifies the logic for determining the animation state. Using the getter ended up passing returning an invalid state in some cases (e.g. `undefined-top` or `undefined-bottom`).

Fixes #7063.
@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.
Assignees

@crisbeto crisbeto

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(snack-bar): subsequent snack bars not opening; animation issues crisbeto/material2
2 participants
@crisbeto @SaturnTeam