Inline elements should have correct Span (not zero-filled) #416

New Issue

claunia · 2026-01-29T14:36:10Z

claunia commented

2026-01-29 14:36:10 +00:00

Originally created by @KvanTTT on GitHub (Nov 9, 2020).

Consider the following markdown fragment:

a `b` **c**

The parser returns ContainerInline node with the following children:

[0] = {LiteralInline} a 
[1] = {CodeInline} `b`
[2] = {LiteralInline}  
[3] = {EmphasisInline} 42 '*' Count: 2

But all Span properties of these nodes are zero-filled (0-0) though they should not.

How can I get the correct position of inline nodes?

Originally created by @KvanTTT on GitHub (Nov 9, 2020). Consider the following markdown fragment: ``` a `b` **c** ``` The parser returns `ContainerInline` node with the following children: ``` [0] = {LiteralInline} a [1] = {CodeInline} `b` [2] = {LiteralInline} [3] = {EmphasisInline} 42 '*' Count: 2 ``` But all `Span` properties of these nodes are zero-filled (`0-0`) though they should not. How can I get the correct position of inline nodes?

claunia closed this issue

2026-01-29 14:36:10 +00:00

claunia commented

2026-01-29 14:36:11 +00:00

@KvanTTT commented on GitHub (Nov 9, 2020):

It works fine if I set PreciseSourceLocation in the following way:

var builder = new MarkdownPipelineBuilder
{
    PreciseSourceLocation = true
};
MarkdownDocument document = Markdown.Parse(content, builder.Build());
return new MarkdownContainerBlockNode(document, ParseHtmlMarkdown(document));

Sorry for the noise.

@KvanTTT commented on GitHub (Nov 9, 2020): It works fine if I set `PreciseSourceLocation` in the following way: ```cs var builder = new MarkdownPipelineBuilder { PreciseSourceLocation = true }; MarkdownDocument document = Markdown.Parse(content, builder.Build()); return new MarkdownContainerBlockNode(document, ParseHtmlMarkdown(document)); ``` Sorry for the noise.

claunia referenced this issue

2026-01-29 14:48:30 +00:00

[PR #416] [MERGED] Random improvements #1006

claunia referenced this issue

2026-01-29 14:48:30 +00:00

[PR #416] Random improvements #1011

Sign in to join this conversation.