Toasts overlapping and displaying for a long time

[add118]

If multiple toasts are created in quick succession, such as pressing submit when the incident isn't completely filled in, they get put into a stack and displayed in order. This means if I press submit 100 times it will toast "incident has not been completely filled in" 100 times for their full duration.

Possible solution I'll be looking into: http://stackoverflow.com/questions/12922516/how-to-prevent-multiple-toast-overlaps?lq=1

[williamvanderkamp]

Thank you, this is an important one.
On Mar 26, 2015 5:24 PM, "add118" notifications@github.com wrote:

If multiple toasts are created in quick succession, such as pressing
submit when the incident isn't completely filled in, they get put into a
stack and displayed in order. This means if I press submit 100 times it
will toast "incident has not been completely filled in" 100 times for their
full duration.

Possible solution I'll be looking into:
http://stackoverflow.com/questions/12922516/how-to-prevent-multiple-toast-overlaps?lq=1

—
Reply to this email directly or view it on GitHub
#47.

[williamvanderkamp]

I think a good solution to this is to grey out the submit button until they
can legally submit.
On Mar 26, 2015 5:24 PM, "add118" notifications@github.com wrote:

If multiple toasts are created in quick succession, such as pressing
submit when the incident isn't completely filled in, they get put into a
stack and displayed in order. This means if I press submit 100 times it
will toast "incident has not been completely filled in" 100 times for their
full duration.

Possible solution I'll be looking into:
http://stackoverflow.com/questions/12922516/how-to-prevent-multiple-toast-overlaps?lq=1

—
Reply to this email directly or view it on GitHub
#47.