This repository was archived by the owner on Sep 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Toasts overlap #4822
Labels
needs: investigation
The cause of this issue is not well understood and needs to be investigated by the team or community
P5: nice to have
These issues will not be fixed without community contributions.
Milestone
Comments
TL:DR - Your fiddle is slightly wrong, but there is still an issue. Toasts aren't overlapping, but if they're cancelled before display, they will never show. My initial thoughts on how to fix this fiddle - wrap the
This might be caused by using |
devversion
added a commit
to devversion/material
that referenced
this issue
Jan 14, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 1, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 1, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 1, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 1, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 7, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 7, 2016
After this patch, the interim stack will pick up the latest element which is not in hide process. At the moment we always take the first, but this one can be in hide progress. Fixes angular#6633 Fixes angular#4822
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 7, 2016
After this patch, the interim stack will pick up the first added element from the stack which is not in hide process. At the moment we always take the first added (not caring about current hide process). Also the stack always removes the elements immediately, which causes errors when showing multiple interims (for example spamming toasts). After this fix, we will remove the elements after the hide-process is done (like a stack queue) Fixes angular#6633 Fixes angular#4822
Closed
This issue is closed as part of our ‘Surge Focus on Material 2' efforts. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
needs: investigation
The cause of this issue is not well understood and needs to be investigated by the team or community
P5: nice to have
These issues will not be fixed without community contributions.
Try http://jsfiddle.net/gm1o55nt/
Expected
5 toasts appear consecutively.
Actual:
You can see only the last toast ('4').
From the spec:
https://material-design.storage.googleapis.com/publish/material_v_4/material_ext_publish/0B6Okdz75tqQsX3VhUHNoaWVEbDQ/components_snackbars_usage_consecutivesbdifferenttype_005.webm
The text was updated successfully, but these errors were encountered: