Story
Magnolia informs me adaquatelyadequately, if an action I take causes caused an error or requires me to note a warning or other textual message. It is important to me that I especially don't miss error messages of long running actions, possibly launched in the background. If I leave my desk and return, I should either still see all messages or have a notification waiting for me informing me that I need to take a look at a message log, since new important messages arrived in my absense.
...
Description of desired behaviour
System messages differ from e.g. validation messages in a number of ways. First, they report important system status changes. As such, they have to be displayed more prominently. Because of this, they but should also only be used scarcely. Second, the context of a system message is usually gone once it's being shown. A As an example, a process running a longer - time might fail eventually, or a regular background cleanup job has discovered an oddity, which requires a warning to be displayed to the user. The message thus shows up in any context. By contrast, a validation message can still be visually related to the field, which caused the problem, when it is displayed.
...
Error messages have to be explicitely acknowledged by closing the message box. They should appear - bang - right into your face and have to interrupt you with whatever you're doing now. Use errors as sparingly as possible.
Warning messages don't show up in the center but at a border. They show up and may be dismissed, but they don't have to - they disappear after a short delay. The difference between warning and informational message is that warning messages show up with a brighter color to get your attention and also light up the message icon indicating new messages if they weren't manually dismissed.
...