`MarkdownRenderer.render` cause render fail

[LincZero]

Please fill out these Check-boxes

• I checked for existing similar feature requests
• I have read the docs and checked that the feature I am requesting is not already implemented
• My feature request consists of only one feature

Is your Feature Request related to a Problem or Annoyance?

No response

Describe the Feature you'd like

The effect I want

(Used with other plugins (anyblock plugin, I am the author of this plugin))

Actual result

The collaboration with buttons plugin was successful (See picture above),
but there were some problems with metabind (see image below)：

• Some btn live/read modes failed to render
• Some btn failed in real time while reading mode succeeded

Analysis of causes

Anyblock Plugin use the MarkdownRenderer.render, it can renders a piece of markdown text and return element.
(Note: The result of re-rendering is the result of reading mode. so in reading mode, it might be better to work with plugins)

But there may be some differences between the ctx of 'MarkdownRenderer.render' and the ctx in reading mode, which may be the reason why it doesn't work: (See the bottom of the picture)

• plugins may decide that something is not working in live mode (despite rendering something in read mode in live mode)
• ctx differences, such as containerEl is no longer div.cm-scroller, but the parent element that triggers MardownRenderer.render

Alternatives

No response

Additional Context

No response

[LincZero]

Repeat tips

when use

```anyblock
```

And the first line in the code block is not [...]

All he does is call the contents of the code block through 'MarkdownRenderer.render', and little else is done.

So you can use this feature to facilitate debugging

test demo

````anyblock
test1
```meta-bind-button
style: primary
label: Meta Bind Help
action:
  type: command
  command: obsidian-meta-bind-plugin:open-faq
```
test2
```meta-bind
INPUT[inputType]
```
test3
`INPUT[toggle]`

test4
`INPUT[inputType]`

test5
```button
name Toggle spellcheck
type comand
action Toggle spellcheck
color blue
```
^button-spellcheck
````

[mProjectsCode]

Are you passing a loaded component to the render function?

[mProjectsCode]

Can you send me the errors that should appear in the console? What does it say when you click on the error message I the rendered content?

[LincZero]

console message

The console did not report an error or print any other information

It simplifies what I do

this.registerMarkdownCodeBlockProcessor("anyblock", ABReplacer_CodeBlock.processor);
...
export class ABReplacer_CodeBlock{
  static processor(
    src: string,
    blockEl: HTMLElement,
    ctx: MarkdownPostProcessorContext,
  ) {
    let dom_replaceEl = blockEl.createDiv({
      cls: ["ab-replaceEl"]
    })
    MarkdownRenderer.render(app, src, dom_replaceEl, app.workspace.activeLeaf?.view?.file.path, new MarkdownRenderChild(dom_replaceEl));
  }
}

This way it can be matched with the plugin

any-block/any-block#74

buttons、dataview、mindmap nextgen、and many other rendering-related plugins.

[LincZero]

A better demo

[mProjectsCode]

Like I suspected, you are not correctly passing a component to the render function. Try something like this.

export class ABReplacer_CodeBlock{
  static processor(
    src: string,
    blockEl: HTMLElement,
    ctx: MarkdownPostProcessorContext,
  ) {
    let dom_replaceEl = blockEl.createDiv({
      cls: ["ab-replaceEl"]
    });
    const mdrc = new MarkdownRenderChild(dom_replaceEl);
    ctx.addChild(mdrc); // you must register your mdrc to the context object. Otherwise stuff won't work correctly any will leak memory
    MarkdownRenderer.render(app, src, dom_replaceEl, app.workspace.activeLeaf?.view?.file.path, mdrc);
  }
}

[LincZero]

Yes, you are right. When I add ctx.addChild, everything goes back to normal.

I've done this in the past, but later removed it for compatibility when migrating to markdown-it (not sure what this step does at the time T_T).

Thank you very much for your help.