Alert notification messages stack unnecessarily and push the rest of the UI down

[sergioc]

When events (messages fail, failed messages successfully archived or retried) occur in rapid succession in the failed messages screen, the UI gets littered with several alert messages, and the rest of the UI is pushed down:

There's a few issues with this:

• the alert style we use is UI pattern that doesn't really work well with a rapid succession of several events
• the messages push the UI down (thus possibly making the user miss a click in the UI (related Desk case)
• they require manual dismissal (possibly a lot of labor involved, depending on no. of messages)

This can be addressed in the following way:

• Remove alerts for failed messages. Instead show a count badge next to the "Failed messages" nav link and clean up the title for the failed messages container. This way it's more clear when it gets updated and the count badge is visible at all times
• Show only a maximum number (e.g. 3) of toast messages for archive and retry successes and dismiss automatically
  • Further improvements could be done by replacing those toast messages with in-context status messages: Status of actions on failed messages do not persist across states/clients #252

Demonstration of problem http://screencast.com/t/MbSRv32fw

[petersgiles]

quick example of badge next to failed messages

[mauroservienti]

this should be prioritized, @ramonsmits and I experienced that in an environment where the failed message throughput is high the SP UI is unusable.

[petersgiles]

@mauroservienti I'm working on it now