This is a breaking change:

• Compatibility with Existing Code: If the ErrorWindow component is widely used in an application, other parts of the application may rely on the current behavior, which allows HTML-formatted error messages. Changing this behavior could break existing code that expects HTML-formatted messages.
• User Expectations: Users of the application may expect error messages to be displayed in a specific format, such as with HTML formatting. Changing this behavior could result in unexpected changes in how errors are presented to users.
• Security Implications: Allowing HTML formatting in error messages can be risky, as it opens up the possibility of script injection attacks, where malicious code can be injected into error messages. While this is a security concern, changing the behavior to interpret messages in a text-only format could break applications that rely on legitimate HTML formatting for error messages.

Close #74