Markdown tables break when wrapped in block-level HTML elements in Tiptap

[nareshreddymandati9177-stack]

Issue: Clarification & Stability of Markdown Tables When Mixed With HTML in Tiptap

We are encountering inconsistent behavior and table breakage in Tiptap when Markdown tables are mixed with block-level HTML elements during Markdown ↔ HTML conversions. This issue is primarily related to how tables are parsed and rendered when wrapped inside block elements such as <div> or <p>, or when block elements appear inside table cells.

Markdown tables render correctly when authored as pure Markdown at the root level. However, once HTML block elements are introduced—either wrapping the table or embedded within table cells—the table structure often breaks, flattens into text, or renders inconsistently inside the editor.

This is a significant concern for our application, as tables are a core content structure. We rely heavily on deterministic Markdown ↔ HTML round-tripping for programmatic content insertion, storage, and rehydration inside Tiptap. When tables break, it leads to UI issues and potential data loss, making it difficult to define a safe, long-term content schema.

Expected behavior
Markdown tables should either:

• Render consistently in Tiptap, or
• Fail in a documented and predictable manner

Additionally, supported and unsupported table structures should be clearly defined so developers can author content safely.

Actual behavior observed

• Tables wrapped in <div> or <p> frequently render as plain text
• Table rows and columns are flattened
• Behavior varies depending on the Markdown → HTML → Tiptap conversion path

Below are representative examples demonstrating working and breaking scenarios.

Example 1 – Works (Plain Markdown table)

| Name | Age |
|------|-----|
| John | 30  |
| Jane | 28  |

Example 2 – Breaks or behaves inconsistently (Markdown table wrapped in <div>)

<div>
| Name | Age |
|------|-----|
| John | 30  |
| Jane | 28  |
</div>


Example 3 – Breaks (Markdown table wrapped in <p>)

<p>
| Name | Age |
|------|-----|
| John | 30  |
| Jane | 28  |
</p>


Example 4 – Unclear support (Block elements inside table cells)

| Description |
|------------|
| <p>Line 1</p><p>Line 2</p> |


or

<table>
  <tr>
    <td>
      <p>Line 1</p>
      <p>Line 2</p>
    </td>
  </tr>
</table>


In these cases, behavior varies: sometimes the content is preserved, sometimes merged into a single paragraph, and sometimes the table structure breaks entirely.
We are seeking clarification on the following points:
Are Markdown tables officially supported when wrapped inside block-level HTML elements such as <div> or <p>?
Are block elements like <p> allowed inside table cells, or should cells contain only inline content?
Is it recommended that Markdown tables always remain at the root level without surrounding HTML?
Is mixing Markdown tables and HTML expected to be lossy in Tiptap?
Are there known or documented structures that are explicitly unsupported?

Additionally, we would greatly appreciate official documentation or guidance covering:
Supported vs unsupported Markdown table structures
Known patterns that cause table breakage
Best practices for safely mixing Markdown and HTML in tables

A recommended “canonical” table format for stable Markdown ↔ HTML conversions in Tiptap
This clarification is important for our architectural decisions. We are actively evaluating a Tiptap Pro license and need a deterministic and well-documented approach for handling tables to proceed confidently.

Environment (can provide exact versions if needed):

Tiptap (latest)
ProseMirror tables enabled
Markdown parsing via marked / turndown
Framework: Angular
Browser: Chrome