CommonMark testing started here!

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)

  • :white_check_mark: Onebox vanishes after you start typing and works not-super consistently

  • :white_check_mark: pending approval does not render

  • :white_check_mark: Quote without preceding empty line does not work.

  • :white_check_mark: Onebox of reply is missing tons of info and not rendering right

  • :white_check_mark: When quoting the composer sometimes inserts a quote block in the middle of a line (not a new bug but broken with new engine)

  • :white_check_mark: Onebox bypass is not working

  • :white_check_mark: Table is not showing up styled in preview

  • :white_check_mark: Details composer toolbar generating inline details

  • :white_check_mark: Emoji → Image conversion (when posing Emoji’s via a phone) is not implemented yet.

  • :white_check_mark: 2 polls in a post seems to be … not that good.

  • :white_check_mark: Sanitizer stripping out right align style for tables

  • :white_check_mark: Some BBCode is unimplemented: [email], [url], [code] and [img]

  • :white_check_mark: Somelink - just another link on the internet :arrow_backward: fails cause of the tag/category plugin

  • :white_check_mark: 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

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.

32 Likes