Outstanding Issues

[aidantwoods]

As a starting point, its probably worth reviewing https://github.com/erusev/parsedown/issues to see where we are in terms of reported unfixed bugs and reopening them here. A reasonable number have already been fixed by changes over here so far (see: erusev#553), and some issues are probably questions/feature requests that can probably be left for now.

Open Issues in Parsedown

(check if fixed)

Bugs with sufficient information

• Safe Mode erusev/parsedown#161, safe mode
• Parse inlineLink incorrectly if the link text is an URL erusev/parsedown#358, Parse inlineLink incorrectly if the link text is an URL
• URL in [...](link) gets Double Linked erusev/parsedown#417, URL in [...](link) gets Double Linked
• the last item of a list missing <p></p> tag erusev/parsedown#427, the last item of a list missing <p></p> tag
• Link parse issue erusev/parsedown#432, Link parse issue
• Unexpected paragraph in unordered list erusev/parsedown#474, Unexpected paragraph in unordered list
• Bug with inlineUrl method - not consider already wrapped anchor with the same URL erusev/parsedown#487, Bug with inlineUrl method - not consider already wrapped anchor with the same URL
• Link allows javascript which could lead to XSS issues erusev/parsedown#497, Link allows javascript which could lead to XSS issues
• Double Parsing!! erusev/parsedown#504, Double Parsing!!
• incorrect render for c# erusev/parsedown#524, incorrect render for c#
• Possible bug when rendering list erusev/parsedown#529, Possible bug when rendering list
• Cross-site scripting vulnerability in ParseDown erusev/parsedown#530, Cross-site scripting vulnerability in ParseDown
• Inconsistent List Formatting With Linebreaks erusev/parsedown#551, Inconsistent List Formatting With Linebreaks
• Parsedown does not treat emphasis tags (*, _, etc.) as literal when spaced out erusev/parsedown#531, Parsedown does not treat emphasis tags (*, _, etc.) as literal when spaced out
• Different result parsedown vs original due to new line erusev/parsedown#528, Different result parsedown vs original due to new line
• The thing with the tab replacement by four spaces erusev/parsedown#508
• Complex URL not parsed properly erusev/parsedown#505
• Invalid parsing syntax in HTML tag erusev/parsedown#488 (fix started in Htmlblocks erusev/parsedown#489)
• <kbd> HTML tag breaks parsing erusev/parsedown#486
• Parsedown is unable to parse correctly of Ordered List with backtick/Fenced Code Block erusev/parsedown#477
• Trimming indentation in block code erusev/parsedown#466 (fix started in Fix #466 erusev/parsedown#467)
• (duplicate of 362) Headers should be a serie of '#' followed by at least one whitespace erusev/parsedown#463 (this is strictly speaking a commonmark violation)
• Maximum nesting level reached erusev/parsedown#462
• Parsedown does not escape * character inside of backticks erusev/parsedown#461
• Incorrect parsing numeric lines erusev/parsedown#454
• Parsedown fails with long text erusev/parsedown#443
• (duplicate of 434) Escape Not Working erusev/parsedown#442
• Incorrect behaviour for mixed list types? erusev/parsedown#437
• Supporting non-ASCII characters as markers erusev/parsedown#435 (fix started in Added tests for unicode content and updated parser to manage utf-8 erusev/parsedown#513)
• Escaping issues erusev/parsedown#434
• line before a table is interpreted as fist col erusev/parsedown#415
• List parse error erusev/parsedown#412
• Header rendering bug erusev/parsedown#411
• According to the web component spec, a dash is required, which breaks md parsing erusev/parsedown#407
• Code breaks parsing erusev/parsedown#405
• Invalid link parsing with right parenthesis erusev/parsedown#375
• Parsedown stops parsing after <img> tag erusev/parsedown#370 (there's a bug here, but not with the test case reported per commonmark – parsedown does some non-compliant things when determining tag nesting)
• Bug with block html element inside markdown erusev/parsedown#367
• BAG if we have html comment right after html close tag erusev/parsedown#366
• Square brackets in links erusev/parsedown#365
• Parsing of "__foo__" error erusev/parsedown#364
• blockHeader function improvement erusev/parsedown#362
• Double quotation (") in image title breaks parsing the image erusev/parsedown#360
• <kbd> and new line in HTML list erusev/parsedown#356
• preg_match in inlineLink() causes segfault erusev/parsedown#352
• Adjacent block quotes rendering issue erusev/parsedown#344
• Headings inconsistent with the original Markdown renderer erusev/parsedown#337
• Documenting the functions in code erusev/parsedown#324 (he's not wrong)
• Changing Line Combination Character in Paragraph erusev/parsedown#320
• Images from data uri erusev/parsedown#299
• Brackets in automatic link conversion erusev/parsedown#292
• Converting Straight-Quotes Discourages Future Processing erusev/parsedown#287 (this probably doesn't happen anymore due to escaping methodology changes)
• Handling of Invalid HTML erusev/parsedown#259
• parse link error erusev/parsedown#246
• Edge cases I commonly run into erusev/parsedown#233
• Emphasis management error erusev/parsedown#198
• (duplicate of 362) Wrong parser erusev/parsedown#174
• em and strong fail if html with _ inside erusev/parsedown#107
• Specify start attribute on ordered lists erusev/parsedown#100

Bugs with insufficient information

• Fails to parse tabs (breaks everything!) erusev/parsedown#549
• String with multiple tabs breaks Parsedown erusev/parsedown#527
• Table column length erusev/parsedown#517
• Parsedown does not convert markdown to html in this case erusev/parsedown#468
• Blockquotes Not Rendering erusev/parsedown#397
• bug in cod (<pre><code>) return empty erusev/parsedown#389
• Table rendering bug erusev/parsedown#383
• Table rendering in parsedown erusev/parsedown#379
• Bug with multibyte text inside li tag erusev/parsedown#378
• Incorrect parse when comments followed by any character erusev/parsedown#288
• Nested ordered lists do not support more than 2 levels of indentation erusev/parsedown#270
• Href attribute not being rendered correctly erusev/parsedown#266
• Rendering ```php+html issues erusev/parsedown#232
• Encoded emails when using 'autolink' erusev/parsedown#193
• Inconsistent List-Parsing with code blocks erusev/parsedown#173
• Indentation erusev/parsedown#75

Meta bugs

• Make parsedown 'CommonMark' ready/compliant erusev/parsedown#213

Feature Requests

• Conflicts With MathJax erusev/parsedown#510
• (duplicate of 510) MathJax erusev/parsedown#554, MathJax
• [Feature Suggestion] Headers are always on a new line erusev/parsedown#542
• Link Target Blank erusev/parsedown#494
• Feature request: remove the PHPUnit_Framework_TestCase class alias erusev/parsedown#490
• add class to code block erusev/parsedown#473
• syntax highlighting erusev/parsedown#472
• Can I enable show line number for code? erusev/parsedown#471
• I cant use syntax highlighting for bash scripts erusev/parsedown#470
• Changing the image sizes in parsedown? erusev/parsedown#460
• Unexpected parsing _underline_ in $LaTeX$ erusev/parsedown#457
• Embed video erusev/parsedown#422
• remove markdown erusev/parsedown#413
• Can't create extension using special characters erusev/parsedown#401
• Parsing inside markdown="1" erusev/parsedown#371
• Inline markup to block in extension erusev/parsedown#348
• Option or extensibility to parse blocks into <p> tags instead of using <br /> tag erusev/parsedown#339
• Run a completion block after text() has processed lines() erusev/parsedown#338
• Giving a header an ID erusev/parsedown#306
• # in image title breaks parsing the image erusev/parsedown#304
• Integrate tests from MarkDown Test Suite erusev/parsedown#112
• Benchmarking erusev/parsedown#102
• Specify value attribute on ordered list items erusev/parsedown#101
• John Gruber's test suite erusev/parsedown#99

Questions

• [Question] Is it possible to ignore certain items such as headers? erusev/parsedown#550
• blockquote not work on my site erusev/parsedown#537
• handler-extensibility erusev/parsedown#523
• Excuse an amateur -- what do I upload where? erusev/parsedown#483
• how to use parsedown in laravel 5.4 erusev/parsedown#476
• How secure is this? erusev/parsedown#418 (answered by setSafeMode)
• when to parse markdown file no style, how to add css file erusev/parsedown#400
• Support for inline images erusev/parsedown#390
• it support Latex? erusev/parsedown#350
• How to: Line break creates a line break erusev/parsedown#326
• Weird I can't figure out. erusev/parsedown#282
• Add public getters/setters for protected properties erusev/parsedown#155

Requests for CommonMark/GFM violations (marking all as done)

• Parsedown never generates <br> break tags / empty lines erusev/parsedown#448
• image tag fails to render when surrounded by <center></center> erusev/parsedown#428 (I think)
• want to have tables without th erusev/parsedown#416
• Multi-line link not detected erusev/parsedown#399
• Parse tables without header erusev/parsedown#301 (but meh, might be useful so could be moved to "feature request")

Other, repo-specific (marking all as done for these purposes)

• Housekeeping erusev/parsedown#553, Housekeeping
• Parsedown on Babelmark2 erusev/parsedown#532
• Tutorial: getting started is missing the "require " line erusev/parsedown#526
• Open some rights on the repository to some people erusev/parsedown#516
• Release erusev/parsedown#503
• The state of the master branch? erusev/parsedown#438
• Documentation erusev/parsedown#159
• No way to link to Markdown/Parsedown comparison on parsedown.org erusev/parsedown#83

Other, unsure how to categorise

• Using sethtmlescaped function prevents emojis to form erusev/parsedown#421
• Add "Caracal" as CMS using this parser. erusev/parsedown#308

[aidantwoods]

I have now categorised all 127 open issues from the Parsedown repository above. I have checked bugs which I do not feel require additional attention (and should be closed in the main repo if possible provided that bug fixes from this repo are merged across). Bugs that are unchecked are either unfixed or I'm unsure about them (either way they need an additional looking at).

I may have missed linking some duplicates, or non-optimally categorised things – please just suggest or make improvements in this case :)

I would suggest that we open issues here to cover non-duplicates from the unchecked items in "Bugs with sufficient information".

[PhrozenByte]

Great work! ❤️

I don't think that it's necessary to open new Issues for the unchecked bugs above, this list should be sufficient to manage them. Discussions should still happen in the existing Issues. Maybe just a small hint that erusev#554 is the latest Issue of this list, so that we can later add new Issues more easily.

What about all those open PRs? You've merged the most important already, but there are surely some more sensible PRs in the repo (not that I want to say that they should be merged immediately, just checked the same ways as you checked Issues).

[aidantwoods]

I think this issue probably isn't needed anymore, since I'm able to tag and close out solved issues in the main repo to keep things organised.

I didn't add any new issues, but figured I might as well tick everything that was closed in the main repo since this was last updated :)