When an error occurs, say after saving a file that doesn't parse, the error message is returned in the page with the structure <div class="container"><h1>message</h1></div>. The display mechanism for errors appears to get the content of the first <h1>. This is open to problems if, for example, a developer changes the layout and includes a heading in that. The workaround is obviously to avoid <h1> in the layout but it would be better to more uniquely identify error content in the response from the server.
This was seen in Callimachus Enterprise 1.4 but has been a potential issue for a long time.
When an error occurs, say after saving a file that doesn't parse, the error message is returned in the page with the structure
<div class="container"><h1>message</h1></div>. The display mechanism for errors appears to get the content of the first<h1>. This is open to problems if, for example, a developer changes the layout and includes a heading in that. The workaround is obviously to avoid<h1>in the layout but it would be better to more uniquely identify error content in the response from the server. This was seen in Callimachus Enterprise 1.4 but has been a potential issue for a long time.