clay
(Clay Heaton)
December 15, 2015, 2:44pm
1
The following text appears not be be parsed properly by Markdown. Here’s an image of what is entered:
Below here shows how it renders
Some fenced code
This should be a list:
List Item One
List Item Two
List Item Three
List Item Four
Some links in another list:
A regular sentence
some more fenced code
1 Like
sam
(Sam Saffron)
December 15, 2015, 10:35pm
2
See my edit…
If you have a tripple quote thing and have a trailing space after the tripple quote stuff gets weird.
Will be far better in our new markdown engine.
4 Likes
clay
(Clay Heaton)
December 16, 2015, 2:01pm
3
By the way – in case it is relevant for development of the new markdown engine – the bad behavior is different when there’s a space after the opening ``` versus the closing ``` of a block.
sam
(Sam Saffron)
June 26, 2017, 8:02pm
4
In the new engine you can have trailing spaces after the closing code fence
And you can even have trailing spaces after opening fence
Per our migration plans , I just enabled markdown.it at Meta.
It is an excellent CommonMark compliant engine. I expect quite a few edges to be found during this period of testing.
Do not open bugs about the new Engine, just reply here.
I/we will be updating the top post here with the list of issues and striking out stuff as it is fixed.
Current known issues (to be fixed)
Onebox vanishes after you start typing and works not-super consistently
pendin…
2 Likes