**<big>This is a test:** End test.</big> Preview shows (image): [image] Actually shows (image for historical reference): [image] Actually shows (text): This is a test: End test. Changing it to <big>**This is a test:** End test.</big> as I’d meant to do shows it correctly and consistently. …

Okay. So I’m curious then, what does the preview and post rendering do differently that can cause inconsistencies?

This is well documented all over the internet, for example http://www.bu.edu/tech/services/cccs/websites/www/non-wordpress/start/html-introduction/syntax/nesting-tags/

I was referring specifically to Discourse’s rendering engine. I get that it’s not supported to use misordered tags. I was just curious if, for example, there are two separate implementations, whether the algorithm is nondeterministic, etc.

There are differences in markup between the preview and topics. Most of them are related to some content being added on the server side (like one boxes), but others are as simple as where it is in the DOM. The composer has a different HTML structure than the posts view, and that’s enough to make a d…

Strangely ordered markdown + HTML is shown differently in post vs. preview

Support

codinghorror (Jeff Atwood) July 31, 2019, 4:55am 2

Inconsistent ordering of tags is not supported in any markup engine, and will always produce unknown and generally bad results.

Topic		Replies	Views
Markdown preview and result differ Bug composer	6	1179	June 20, 2023
"Traditional markdown linebreaks" not reflected in preview Bug	3	1433	July 3, 2017
Incoming HTML Email Inconsistent Support	4	1085	September 4, 2017
The "button" HTML5 tag renders in the editor previewer, but not rendered posts Bug	9	241	March 26, 2025
Discourse doesn't follow the CommonMark spec for HTML <pre> tags inside code spans Bug markdown-it-review	5	2590	June 26, 2017

Strangely ordered markdown + HTML is shown differently in post vs. preview

Related topics