-
-
Notifications
You must be signed in to change notification settings - Fork 873
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
Support for <sub> #16
Comments
Commonmark doesn't specify any type for it, but html should be supported. I suspect the sloppy inline html parsing is causing this, but can't check right now. What does it get converted to? |
Sorry I missed that in the original issue. It is converting |
Hrm, yeah. I really have to get the inline HTML handling fixed. No solution for this right now, unfortunately. |
+1 As I need support for |
I tracked this down to this line; It seems that all |
@rexxars Could you do a regex on |
Oh, actually, this is related to rexxars/commonmark-react-renderer#9 I'll continue discussion there. |
The new release candidate for v3 has (very basic) support for attributeless, inline html nodes. Please read this issue for more information. Please give it a go and let me know if you encounter issues. |
@rexxars Coming into this in 2020, I don't see an easy way of using the tag other than enabling "allowDangerousHtml". Any clues here? |
Hi is there any plans to support superscript in this markdown parser? I tried using
<sub>1</sub>
but this tag gets converted to even if I specifyskipHTML
option.The text was updated successfully, but these errors were encountered: