Notification Categories

[andrewazores]

Since #245 / #255, notifications go into a drawer with the most recent entry at the top, organized purely chronologically. It might be more useful for users if notifications were grouped by either notification category (as in WebSocket notifications channel "category" key), or by graphical notification level, and sorted chronologically within those categories.

[jan-law]

If you look at my rough demo screenshots, I wanted to separate the notifications that confirm user actions from the notifications that show target info. The warnings/errors have their own category to make it easier for users to find the error again after they close the toast notification. What do you think of the notification category grouping and header titles?

Also, if there are many “Completed Actions”, the “Network Info” and “Problems” headers aren’t visible until you scroll down, which could be confusing if users see an error toast notification and don’t know where the notification went.
Patternfly guidelines suggest no more than 3-4 categories and that only one category is expanded at a time. To fix the problem, I was thinking of automatically expanding the “Problems” category if there’s at least one unread error. What do you think?

[andrewazores]

I was thinking of automatically expanding the “Problems” category if there’s at least one unread error. What do you think?

That sounds like a really good idea to me. Looks excellent so far.