diff options
author | Waylan Limberg <waylan@gmail.com> | 2014-01-12 18:17:37 -0500 |
---|---|---|
committer | Waylan Limberg <waylan@gmail.com> | 2014-01-12 18:17:37 -0500 |
commit | 28d61f5b6b1e0863857c9e1368b3f7698c2f67dd (patch) | |
tree | f85576ea19da02d9717ebf34e9b0edfdc3ec7d28 /tests/extensions/extra/named_markers.txt | |
parent | d0e088d535a478b9435ff49fd27583f5cb9c2641 (diff) | |
download | markdown-28d61f5b6b1e0863857c9e1368b3f7698c2f67dd.tar.gz markdown-28d61f5b6b1e0863857c9e1368b3f7698c2f67dd.tar.bz2 markdown-28d61f5b6b1e0863857c9e1368b3f7698c2f67dd.zip |
Improved multiline comment parsing.
Fixes #257 and slightly alters comment parsing behavior.
Unlike self-closing tags, a comment can contain angle brackets between the
opening and closing tags. The greaterthan angle bracket at the end of the
first block should not be mistaken for closing the comment. Need to actually
check for a comment closing tag (`-->`). If one if not found, then the comment
keeps going (to the end of the document if nessecary) just like in HTML.
That last bit is a slight change from previous behavior, but should be
unsurprising as that's how broswers parse html comments. And as far as
I can tell, more implementations follow this behavior than any other. The
ones that don't seem to be all over the place.
Diffstat (limited to 'tests/extensions/extra/named_markers.txt')
0 files changed, 0 insertions, 0 deletions