Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some markdown elements not parsed for content with inline html #1195

Closed
mjbvz opened this issue Apr 2, 2018 · 2 comments · Fixed by #1135
Closed

Some markdown elements not parsed for content with inline html #1195

mjbvz opened this issue Apr 2, 2018 · 2 comments · Fixed by #1135
Labels
L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue

Comments

@mjbvz
Copy link

mjbvz commented Apr 2, 2018

Marked version: 0.3.19

Markdown flavor: CommonMark

Expectation

Rendering the markdown:

<table>
</table>
<br>

## h1

1. a
1. **b**

<table>
</table>

Result

Heading and list not parsed. Here's the html output:

<table>
</table>
<br>

## h1

1. a
1. <strong>b</strong>

<table>
</table>
@UziTech UziTech added L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue and removed L1 - broken Valid usage causes incorrect output OR a crash AND there is no known workaround for the issue labels Apr 3, 2018
@UziTech
Copy link
Member

UziTech commented Apr 3, 2018

Looks like the problem is in the html regex

...closed *(?:\n{2,}|\s*$)...

says there must to be 2 \n after a closing tag or just white space.

This apparently has to do with the common mark example #199

@joshbruce joshbruce added this to To Do in No known issues via automation Apr 4, 2018
@joshbruce
Copy link
Member

#985

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L2 - annoying Similar to L1 - broken but there is a known workaround available for the issue
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants