*Created by: Elmervc* I was migrating our project to use flexmark instead of pegdown, when I came across the following issue with link reference defs. ## Example markdown: ``` This note demonstrates some of what [Markdown][1] is capable of doing. .... *Note: the fourth item uses the Unicode character for [Roman numeral four][2].* [1]: http://daringfireball.net/projects/markdown/ [2]: http://www.fileformat.info/info/unicode/char/2163/index.htm ``` ### Expected result: This note demonstrates some of what [Markdown][1] is capable of doing. .... *Note: the fourth item uses the Unicode character for [Roman numeral four][2].* [1]: http://daringfireball.net/projects/markdown/ [2]: http://www.fileformat.info/info/unicode/char/2163/index.htm ### Given result (using CommonMark profile): <p>This note demonstrates some of what <a href="http://daringfireball.net/projects/markdown/">Markdown</a> is capable of doing.<br>....<br><em>Note: the fourth item uses the Unicode character for [Roman numeral four][2].</em></p> <p>[2]: http://www.fileformat.info/info/unicode/char/2163/index.htm</p> ------ CommonMark spec: >A link reference definition consists of a link label, indented up to three spaces, followed by a colon (:), optional whitespace (including up to one line ending), a link destination, optional whitespace (including up to one line ending), and an optional link title, which if it is present must be separated from the link destination by whitespace. No further non-whitespace characters may occur on the line. ------ When I add an additional newline between the definitions, or when I remove the indentation (2 spaces) from the definitions, it parses/renders correctly.