Originally Posted by Alexander Turcic
Definitely going to look into that today!
I believe the issue has been fixed. It was triggered by the &&break; in geekmaster's code. An over-simplified regular expression in our Ajax handling code considered this piece a valid HTML entity and therefore decided to encode it into &&break;. We replaced the regular expression with something more robust.