-
Notifications
You must be signed in to change notification settings - Fork 80
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
Markdown syntax is not processed within span-level tags. #31
Comments
On the other hand, whatever is being used to process GFM in this comment, correctly processes markedown inside spans, see below This example shows a bullet list:
|
Fixed on master. |
I believe the fix is not (completely) correct.
should be parsed as
which is not what Maruku trunk does. There's a (partial?) fix on my branch. But I don't think it handles Markdown inside of nested span-level elements as Gruber intends (?). |
@distler you're absolutely right. Testing other engines, it looks like the rule is that if there's a bare HTML element, and it's a block element, then nothing should be parsed within it. If it's HTML within Markdown, or a bare HTML element that's a span element, then it does get Markdown parsed within it. I'll reopen this, add some tests, and fix the logic. |
As is frequently the case, the intended behaviour is not entirely clear.
It's pretty unambiguous that the first two should be parsed as
It's not entirely clear how the 3rd one is supposed to be parsed, but "most" Markdown interpreters seem to parse it as
whereas my implementation (currently) treats it as
|
I wrote:
Fixed properly, now. |
Fixed in your branch? Let me know if you need a hand to bring the changes over here in a PR. |
Fix is now on trunk. |
The markdown spec specifies "Unlike block-level HTML tags, Markdown syntax is processed within span-level tags.", yet maruku does not adhere to this rule. Any markdown within html tags seems to be ignored:
Generates:
Edit:Added code tags
The text was updated successfully, but these errors were encountered: