Is filter |markdown supposed to bypass autoescape?

[pamtbaau]

When content/variable is considered save, we can use filter |raw to bypass autoescaping.

Although it has a completely different function, filter |markdown has the same effect. Is that by design or an unforeseen side-effect?

For example below snippets both show the alert when the page is rendered:

{{ '<script>alert("Hello filter raw")</script>'|raw }}
{{ '<script>alert("Hello filter markdown")</script>'|markdown }}

[mahagr]

The short answer is yes. Markdown allows HTML tags to be used freely without any restrictions.

[pamtbaau]

Thanks.

Forgot to ask: I've seen themes using {{ page.content | markdown }} instead of |raw. Does it make sense to parse again already parsed Markdown?

[rhukster]

Content should already be markdown processed, so that does sound redundant. However, if you have a custom field in frontmatter that contains markdown, the filter makes sense.