Skip to content
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.

Toast Queuing #1144

Closed
rschmukler opened this issue Jan 8, 2015 · 4 comments
Closed

Toast Queuing #1144

rschmukler opened this issue Jan 8, 2015 · 4 comments
Assignees
Milestone

Comments

@rschmukler
Copy link
Contributor

When a toast is already showing, and another one is called to be displayed, should the existing toast be immediately dismissed, or should it stay there until the timeout, and then show the next one?

Should this be configurable?

@epelc
Copy link
Contributor

epelc commented Feb 6, 2015

I haven't seen this in android but we could also stack the notifications as they come in and dismiss them from the top with their regular timers.

@rschmukler
Copy link
Contributor Author

Talked to the UX team on this one, the preferred behavior is:

A second toast causes the existing one to immediately start animating out.
Once the existing one has animated out, the new one animates in.

@epelc
Copy link
Contributor

epelc commented Feb 7, 2015

@rschmukler Just as a note the current behavior is the new toasts begin animating in while the old ones are animating out which makes them overlap.

@rschmukler
Copy link
Contributor Author

@epelc yup, just fixed 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants