HTML renderred by wagtail-markdown is not recoginzed as HTML contents by browser about wagtail-markdown HOT 2 CLOSED

I figured out myself, it is a very basic knowledge point (HTML Escaping) for Django actually. Apply safe Django template filter solves the problem.

in template file: Post_Detail.html

{% load wagtailmarkdown %}
<div class="markdown">
      {{ page.html_body|safe }}  
</div>

However, my original intention is minimize the workload of web server every time when the page is loaded by viewers.

So, I am wondering whether I should get rid of this safe or any template filter to further reduce the workload ? If yes, then how please ? I did not see possibility for saving {{ page.html_body|safe }} in database.

from wagtail-markdown.

|safe is a tempalte tag that uses mark_safe to mark the string as "safe" to be displayed unescaped in the template.

This is what render_markdown does too. However the fact that you mark it as safe then store it in the database means you're saving the processed HTML to the database, which by all intents and purposes is raw HTML which Django correctly encodes when output in the template, so using |safe is the way to go.

Given the above, I am closing this as this is working as intended by Django

from wagtail-markdown.