Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

tryParseMarkdownToBlocks throws on a numbered or check list item that starts with <details>

Aberta
  • Algo errado?
#3,189 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@jkugsiya já está trabalhando nisso.

Desde 14/10/2026.

  • #3194 de @jkugsiya — aberto

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
html, markdown, typescript
Domínio
frontend

Direção de pesquisa

Start by reproducing with editor.tryParseMarkdownToBlocks("1. <details>") and checking the HTML from markdownToHTML for the same input. The likely cause is the toggle list item's details parse rule matching inside numbered and check list items, which leaves a blockContainer with a blockGroup but no blockContent. Done when the table's throwing inputs return blocks without error, and Markdown from blocksToMarkdownLossy loads again.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

What’s broken?

editor.tryParseMarkdownToBlocks throws when a numbered or check list item starts with a <details> tag:

Error: blockContainer node does not contain a blockContent node in its children: blockContainer(blockGroup(blockContainer(paragraph)))

The editor can produce this Markdown itself. Type <details> as plain text in a numbered list item, and blocksToMarkdownLossy exports 1. <details>. Loading that export back throws, so a document saved as Markdown can no longer be opened.

Markdown Result
1. <details> throws
- [ ] <details> throws
1. <details> followed by indented <summary>s</summary>, body, </details> throws
- <details> ok (toggleListItem)
<details> ok (toggleListItem)
1. text <details> ok (numberedListItem)
1. <div> ok (numberedListItem)
1. <summary> ok (numberedListItem)

markdownToHTML("1. <details>") gives <ol><li><p><details></p></li></ol>. My guess is that the toggle list item's details parse rule matches inside a numbered or check list item and leaves the outer blockContainer with a blockGroup but no blockContent.

What did you expect to happen?

tryParseMarkdownToBlocks returns blocks for any Markdown, keeping what it cannot represent as text. At the least, Markdown that blocksToMarkdownLossy wrote should load again.

Steps to reproduce

Default schema, no extensions:

import { BlockNoteEditor } from "@blocknote/core";

const editor = BlockNoteEditor.create();

// 1. Parsing throws.
editor.tryParseMarkdownToBlocks("1. <details>");

// 2. The editor's own export does not load again.
editor.replaceBlocks(editor.document, [
  { type: "numberedListItem", content: "<details>" },
]);
const markdown = editor.blocksToMarkdownLossy(editor.document); // "1. <details>\n"
editor.tryParseMarkdownToBlocks(markdown); // throws

In an app: type 1. and then <details> in an editor, save the document with blocksToMarkdownLossy, and load it with tryParseMarkdownToBlocks.

BlockNote version

v0.55.0 (also v0.54.0)

Environment

Chromium 151 on macOS 15 with React 19 (v0.54.0), and Node 24 with jsdom 30 (v0.54.0 and v0.55.0). Same error in both.

Additional context

Possibly related to #1711, which reported the same error message for a different input and was closed as working.

Linguagem predominante
TypeScript
Estrelas
10.3k
Forks
777
Merge médio
2d 18h
PRs com merge (30d)
41

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TypeCellOS/BlockNote

Todas as issues de TypeCellOS/BlockNote

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.