I'm using the Multimarkdown processor with Highlight Markdown Syntax erros checked. Attached is what I see with proofing on and the Swiss style sheet (if that makes a difference) with the problematic part in context (which might also make a difference, though even the minimal example I shared doesn't flag a problem on my end) no indication there is a problem) ... this is obviously item #4 :)
I only see that there's a missing file if I hover over the link that otherwise doesn't show a problem.
Brett on 20 Jul, 2020 04:11 PM
On my end, your Markdown definitely renders as shown in my original
screenshot, with the obviously-bad link showing up as malformed. I'm not
sure why your processor is turning that into any kind of valid link and
In answer to the question, though, Marked's link checking has two
separate parts. The "Validate Links" feature scans only for 'http' urls
and looks for response codes from visiting those urls. The link hover,
on the other hand, will recognize a file link and do a quick request to
the filesystem to get info on the linked file. But that functions
separately from url validation. I _could_ feasibly add filesystem checks
to the Link Validation feature, but there are many cases where links in
a document aren't expected to work at the time of rendering, and are
instead placeholders or fragment links, which makes it harder to
universally determine that a link is bad.
In your particular case, the processor should be leaving the square
brackets and parens in the final output, which Marked _does_ recognize
as the result of a malformed link. Again, I'm not immediately certain
why you're not seeing that happen. Because it's generating a valid HTML
`<a>` tag for it, it's not triggering Marked's detection of the
malformed link. Like I said, I loaded your provided Markdown using the
MMD processor and did _not_ get the same result as you, so I'm going to
have to do some digging to see if I can replicate.
Is there any chance you have a Custom Processor running?