-
Notifications
You must be signed in to change notification settings - Fork 25
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 open tags. #13
Comments
In HTML 5, certain tags can omit their end tags and still be valid markup. In the HTML 5 spec's section on optional tags, the following elements are listed as having optional end tags:
The spec lists the rules for when each tag would be implicitly closed, so that can be a nice starting point for researching how feasible this is with the current parser's design. |
I ended up using But still, since this package is basically the only way to render HTML string in Elm, I think we should consider this ticket. @hecrj let us know what you think. |
The parser must definitely support the whole spec. Therefore, this is missing functionality. However, I don't think I will be able to invest time on this soon. If anyone else is willing to give it a shot, by all means go for it! I will gladly code review any efforts. I think a good starting point, before starting with the implementation, would be to set up an exhaustive test suite. We seem to be dealing with a bunch of different cases, each one with its own rules. |
In addition, I was having problems with unclosed |
Having an issue with using the HN api.
The HTML they send is not closing some tags (
<p>
for example ).I can assume this is not "valid HTML" but all browsers support it.
Can we have some option to accept it as well in the parser?
Example :
and value is under
text
:The text was updated successfully, but these errors were encountered: