When a blocks3 (scratchblocks) code fence is the last element inside a [!TASK] callout blockquote, it renders correctly. But adding any further content after the fence (still inside the blockquote) breaks the rendering, and the blocks fall back to plain text.
Works (renders the block):
> [!TASK]
>
> Intro text
>
> ```blocks3
> when green flag clicked
> ```
Broken (block renders as plain text):
> [!TASK]
>
> Intro text
>
> ```blocks3
> when green flag clicked
> ```
>
> Outro text
Expected: the when green flag clicked block renders identically in both cases, regardless of trailing content.
Actual: with trailing "Outro text", the fence is not picked up by the scratchblocks renderer and displays as raw monospace text (see screenshots).
The trigger appears to be content following the closing fence within the same blockquote, suggesting the renderer's fence detection doesn't correctly handle a blocks3 block that isn't the final child of the callout.
When a
blocks3(scratchblocks) code fence is the last element inside a[!TASK]callout blockquote, it renders correctly. But adding any further content after the fence (still inside the blockquote) breaks the rendering, and the blocks fall back to plain text.Works (renders the block):
Broken (block renders as plain text):
Expected: the
when green flag clickedblock renders identically in both cases, regardless of trailing content.Actual: with trailing "Outro text", the fence is not picked up by the scratchblocks renderer and displays as raw monospace text (see screenshots).
The trigger appears to be content following the closing fence within the same blockquote, suggesting the renderer's fence detection doesn't correctly handle a
blocks3block that isn't the final child of the callout.