Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 3
    I suspect that our server-side renderer is tripping because you didn't use leading/trailing spaces after the | characters of your tables. You shouldn't have to use spaces, of course, but my hypothesis is if you added them, it'd work properly - so this might work as a workaround for now. I'll do some digging and see if I can reproduce.
    – Ham Vocke StaffMod
    Commented Dec 1, 2020 at 8:08
  • 4
    So now you found a bug: in the current revision (the 3rd) the preview shows the penultimate row with "leading" in the Spaces column, while the saved version shows it in the Link one with a full content of https://meta.stackexchange.com/q/336526|leading|. Commented Dec 1, 2020 at 8:21
  • 8
    @fedorqui'SOstopharming' thanks for breaking this down, this is helpful. Looks like this is an issue with Markdig's link parser (it seems to interpret | as part of a URL which isn't allowed according to the official RFC). This will take a fix in Markdig itself which will take us a bit longer since we've got to coordinate those changes. For the time being: Use spaces, please.
    – Ham Vocke StaffMod
    Commented Dec 1, 2020 at 8:41
  • 2
    @HamVocke so status-deferred or planned?
    – Luuklag
    Commented Dec 1, 2020 at 9:27
  • 3
    @Luuklag deferred. This is not in our hands alone so I can't make any promises about the timeliness of a fix.
    – Ham Vocke StaffMod
    Commented Dec 1, 2020 at 9:44