You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2019. It is now read-only.
ends up treating the text node as a sibling to the <li> rather than as a child. Depending on whether slowparsing is doing the right thing this may or may not require fixing
The text was updated successfully, but these errors were encountered:
I found an example where improper behavior for optional closing tags creates a parsing error, the following will raise a MISMATCHED_CLOSE_TAG error in slowparse:
you're right. the spec says An li element's end tag may be omitted if the li element is immediately followed by another li element or if there is no more content in the parent element. so this is definitely a bug.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
the DOM that is build for text nodes such as
ends up treating the text node as a sibling to the
<li>
rather than as a child. Depending on whether slowparsing is doing the right thing this may or may not require fixingThe text was updated successfully, but these errors were encountered: