# Markdown isn't parsing/displaying some content properly
**URL:** https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743
**Category:** Bug
**Tags:** markdown-it-review
**Created:** [December 15, 2015, 2:44pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743 "2015-12-15T14:44:47Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@clay](https://meta.discourse.org/u/clay)
#### Post date: [December 15, 2015, 2:44pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743/1 "2015-12-15T14:44:47Z")
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
```plaintext
Some fenced code
```
This should be a list:
1. List Item One
2. List Item Two
3. List Item Three
4. List Item Four
Some links in another list:
- [http://www.google.com](http://www.google.com)
- [http://www.yahoo.com](http://www.yahoo.com)
A regular sentence
```plaintext
some more fenced code
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [December 15, 2015, 10:35pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743/2 "2015-12-15T22:35:30Z")
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.
---
### Author:  [@clay](https://meta.discourse.org/u/clay)
#### Post date: [December 16, 2015, 2:01pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743/3 "2015-12-16T14:01:43Z")
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.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 26, 2017, 8:02pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743/4 "2017-06-26T20:02:08Z")
In the new engine you can have trailing spaces after the closing code fence
```plaintext
And you can even have trailing spaces after opening fence
```
🎊
> [@CommonMark testing started here!](https://meta.discourse.org/t/commonmark-testing-started-here/65121):
>
> Per our [migration plans](https://meta.discourse.org/t/discourse-commonmark-migration-plans-confetti-ball-balloon), I just enabled [markdown.it](https://github.com/markdown-it/markdown-it) at Meta. It is an excellent [CommonMark](http://commonmark.org/) 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)white_check_mark Onebox vanishes after you start typing and works not-super consistently white_check_mark pending…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 26, 2017, 8:02pm UTC](https://meta.discourse.org/t/markdown-isnt-parsing-displaying-some-content-properly/36743/5 "2017-06-26T20:02:12Z")