Return to Answer

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear. Here's an example:

$\begin{notanenvironment} \notacommnd \end{notanenvironment}$

For me, on Chrome 45.0.2454.101, HTML-CSS renders with the box as previously.

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear. Here's an example:

$\begin{notanenvironment} \notacommnd \end{notanenvironment}$

For me, on Chrome 45.0.2454.101 in Windows 10, HTML-CSS renders with the box as previously.

Note that when I jump to this answer directly, it remains as [Math processing error] (in red). (And when editing this answer the preview remains in this state for seconds -- after rerendering for every keystroke -- then returns to blank as described above, if you wait.)

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear. Here's an example:

$\begin{notanenvironment} \notacommnd \end{notanenvironment}$

For me, on Chrome 45.0.2454.101, HTML-CSS renders with the box as described in that question's comments.

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear. Here's an example:

$\begin{notanenvironment} \notacommnd \end{notanenvironment}$

For me, on Chrome 45.0.2454.101, HTML-CSS renders with the box as previously.

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear, such as here.

For me, on Chrome 45.0.2454.101, HTML-CSS renders with the box as described in that question's comments.

When using Common HTML, bad formats display as [Math processing error] for a moment then just disappear. Here's an example:

$\begin{notanenvironment} \notacommnd \end{notanenvironment}$

For me, on Chrome 45.0.2454.101, HTML-CSS renders with the box as described in that question's comments.