-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
According to the web component spec, a dash is required, which breaks md parsing #407
Comments
The following seems to fix it: Line 676: Ditto on line 1277: Line 1261: This changed regex allows custom element names such as -- edit: after studying the WHATWG document again: -- edit2: changed the regexp to validate as well as and (line 1261) which didn't work before. |
@pablotheissen: Don't make it overcomplicated, Parsedown is no HTML validator, it's just about matching HTML elements, not about validating them. So, just add the |
What about namespaces? Example /<[\w:.-]+(\s[^<>]*?)?>/ |
Provided that you include a newline between the HTML and the markdown following it this should work as expected in the next release :) |
If you are using web components in your html / md, you must have a dash. For example:
Invalid:
<mycomponent></mycomponent>
Valid:
<my-component></my-component>
The former case stops further parsing of markdown. For example:
Works:
<mycomponent></mycomponent>
# header
Doesn't work:
<my-component></my-component>
# header
In the second case, # header is not converted to an H1 tag, but it should be.
The text was updated successfully, but these errors were encountered: