Anchor checking fails when the close of a fence block is indented more than the open

[dagardner-nv]

The issue happens when the heading follows fenced code block where the closing back-ticks are indented more than the opening of the code block and the next section contains a properly formatted fence block.

I'm not sure if this is valid markdown or not. If it is invalid a parsing error would be nice.

Repro:
test.md

$ markdown-link-check --version
3.13.7
$ markdown-link-check  test.md

FILE: test.md
  [✓] #working-anchor
  [✖] #broken-anchor

  2 links checked.

  ERROR: 1 dead links found!
  [✖] #broken-anchor → Status: 404

[github-actions]

This issue has been marked as stale because it has been open 60 days with no activity. It will be closed in 90 days unless the stale label is removed or someone adds a comment.

[dagardner-nv]

This is still an issue

[dfl-aeb]

I experienced a similar issue with inline HTML.

Adding a <br> tag to one section broke the link checker.

[BaseMax]

I experienced a similar issue with inline HTML.

Adding a <br> tag to one section broke the link checker.

Many thanks for the report. Can you please provide a full example input? @dfl-aeb

[github-actions]

This issue has been marked as stale because it has been open 60 days with no activity. It will be closed in 90 days unless the stale label is removed or someone adds a comment.

[vismam]

I'm observing the same issue, but in this case it's when using more than three backticks, which is useful for nested fenced blocks.

I have also noticed that the second fenced block doesn't need to be in the subsequent section. It could be anywhere after the suspicious fenced block. Actually, any anchors between the suspicious fenced block and the next one will lead to broken links.

test.md

  ERROR: 2 dead links found in test.md !
  [✖] #broken-anchor → Status: 404
  [✖] #second-broken-anchor → Status: 404