#1

Steps to reproduce

if I make an HTML table with blank lines in between (the blank lines are required to get Markdown formatting), the table is ended at the line break… example Markdown with HTML:

<table class="border"><tbody><tr><td colspan="2" style="background-color: DarkBlue;">

**[1](../../../bible/genesis/genesis.1.md):1 Summary Prologue**

In the beginning, God **created** <span style="background-color: DarkRed">the skies and the land</span> [7 words]

</td></tr><tr><td colspan="2" style="background-color: DimGray;">

**[1](../../../bible/genesis/genesis.1.md):2 Exposition of Prologue in 3 lines**

<span class="Bible">Now, <span style="background-color: DarkRed">the land</span> was wild and waste</span> (<span class="foreign">תֹ֙הוּ֙ וָבֹ֔הוּ</span> ([*tōhû<!-- tohu -->* 9332/​8414)](https://ref.ly/logos4/Guide?t=My+Bible+Word+Study&lemma=lbs/he/תֹ֙הוּ֙)[†](logos4:Guide;t=My_Bible_Word_Study;lemma=lbs/he/תֹ֙הוּ֙) *w-*[*bōhû<!-- bohu -->* (983/922)](https://ref.ly/logos4/Guide?t=My+Bible+Word+Study&lemma=lbs/he/בֹּהוּ)[†](logos4:Guide;t=My_Bible_Word_Study;lemma=lbs/he/בֹּהוּ) \[[WP](https://en.wikipedia.org/wiki/Tohu_wa-bohu)])\
 <span class="Bible">and darkness was over the face of the deep abyss</span> ([<span class="foreign">תְה֑וֹם</span> *tehôm<!-- tehom -->* 9333/​8415](https://ref.ly/logos4/Guide?t=My+Bible+Word+Study&lemma=lbs/he/תְה֑וֹם)[†](logos4:Guide;t=My_Bible_Word_Study;lemma=lbs/he/תְה֑וֹם) \[[WP](https://en.wikipedia.org/wiki/Tehom)]) &nbsp; [7 × 2 words]\
  <span class="Bible">but the breath of Elohim was hovering over the face of the waters</span> ([<span class="foreign">הַמָּֽיִם</span> *hamǎyim<!-- hamayim -->* 4784/​4325](https://ref.ly/logos4/Guide?t=My+Bible+Word+Study&lemma=lbs/he/מַיִם)[†](logos4:Guide;t=My_Bible_Word_Study;lemma=lbs/he/מַיִם))

</td></tr>
<tr><td style="text-align: center;">Day 1</td><td style="text-align: center;">Day 4</td></tr>
<tr><td style="text-align: center;">Day 2</td><td style="text-align: center;">Day 5</td></tr>
<tr><td style="text-align: center;">Day 3</td><td style="text-align: center;">Day 6</td></tr>
<tr><td colspan="2" style="background-color: DarkBlue;">

**[2](../../../bible/genesis/genesis.2.md):1 Summary Epilogue**

“Thus were finished <span style="background-color: DarkRed">the skies and the land</span> and all their host

</td></tr><tr><td colspan="2" style="background-color: DimGray;">

**[2](../../../bible/genesis/genesis.2.md):2-3 Exposition of Epilogue in 3 lines**

1. <span class="Bible">And God <span style="background-color: DarkGreen">completed on the <u>seventh</u> day his work which he had **made**</span></span> &nbsp; [7 words]
2. <span class="Bible">And he rested on the <u>seventh</u> day from all his work which he had **made**</span> &nbsp; [7 words]
3. <span class="Bible">And God blessed the <u>seventh</u> day and sanctified it</span> &nbsp; [7 words]\
    <span class="Bible">because on it he rested from all his work which God <u>**created to make**</u></span> &nbsp; [key word of [1](../../../bible/genesis/genesis.1.md):1]

</td></tr></tbody></table>

Expected result

table renders correctly (screenshot from VS Code)

vscode
vscode1043×488 17.8 KB

Actual result

table renders wrong (screenshot from Obsidian)

obsidian
obsidian907×534 23.2 KB

Environment

  • Operating system:

same results in both Windows and Android

  • Debug info:

Additional information

#2

Variations of this report have appeared several times.
Please search before posting.

We intentionally do not support parsing markdown syntax and blank lines within HTML blocks. This is the result of an optimization to handle very large files and to support synchronization between editing and reading mode.

#3

I don’t understand the comment… in Markdown, if there’s blank lines between the HTML & the Markdown, the HTML should get dumped to output untouched… clearly Obsidian is going out of its way to mangle that raw HTML, something I’ve never seen another Markdown processor do

I’ve seen the opposite, where if I don’t put the blank line, the Markdown is ignored and dumped into the HTML output as raw text… but that’s not what’s happening here

so this bug report is saying MD processing is defined to work like X, but in Obsidian it works like Y… if that’s a “feature”, then it means that Obsidian does not support vanilla Markdown… if Obsidian does support Markdown that’s compatible with other parsers, then it’s a bug because it violates the standard

#4