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 -
pending approval does not render
-
Quote without preceding empty line does not work.
-
Onebox of reply is missing tons of info and not rendering right
-
When quoting the composer sometimes inserts a
quoteblock in the middle of a line (not a new bug but broken with new engine) -
Onebox bypass is not working
-
Table is not showing up styled in preview
-
Details composer toolbar generating inline details
-
Emoji → Image conversion (when posing Emoji’s via a phone) is not implemented yet.
-
2 polls in a post seems to be … not that good.
-
Sanitizer stripping out right align style for tables
-
Some BBCode is unimplemented:
[email],[url],[code]and[img] -
Somelink - just another link on the internet
fails cause of the tag/category plugin -
Mention after paragraph is strange
-
Can add any oneboxes after an IMG tag
-
:email, class_name: is not an emoji
-
https://medium.com/@nicksantos not autolinked
New features
-
All of this: http://spec.commonmark.org/0.27
-
Support for GFM tables per: https://help.github.com/articles/organizing-information-with-tables/ (enabled by default)
-
Support for a basic “typographer” see: https://markdown-it.github.io/ to enable set
enable_markdown_typographerto true
Issues that will not be fixed
-
Mixing inline and multiline BBCode will no longer be supported.
-
Core will not implement
[ul][ol]and[li]support for BBCode cause it is a recipe for failure.
This topic is wiki, if you are TL3 or above feel free to clean it up.