This will likely require an API update to work well, but yeah, apparently we're currently assuming that all post/reply content coming from the server is in HTML format.
We could theoretically solve this by rendering all content as markdown+HTML, but this may cause problems with posts written in the HTML editor which happen to use markdown-relevant characters (such as starting a line with # ).