Status Message should allow a minimum of formatting, such as line breaks (either in the form \n or <br/>).
Keeping those simple tags should not present a security risk, and would make Status Message a lot more usable :
Currently a long message will take all or most of the page width on a single, which makes it real hard for a user to read : bad for adoption.
Suggested workaround to use a popup is really not convenient.
Furthermore, when a service si configured to "Show error notification" and throws an error message containing a \n, the \n are converted to <br/> but the "Status Message" (not 100% that is the same widget) is not supporting it and it renders as "text".
So, PTC, at least be consistent and remove \n instead of changing it to something that does not render properly (but allowing it would be better).