Skip to content

Treat <ol> like <ul> when parsing as HTML #23

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

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

cyanogilvie
Copy link

<ol>
<li>first
<li>second
</ol>

was failing to parse with -html set. This patch adds the <ol> tag to the set that trigger autoclose.

I also added test cases to highlight the incorrect nesting of the <li> child nodes when this doc is parsed.

cyanogilvie and others added 5 commits February 9, 2015 12:23
Currently they still fail because <ul><li>first<li>second</ul> is interpreted as
<ul><li>first<li>second</li></li></ul> instead of
<ul><li>first</li><li>second</li></ul>
-breakLines outputs "\n>" instead of ">" for the opening tags of elements.
This makes it less likely that there will be excessively long lines in the
output which break HTML emails - lines longer than 998 chars can be wrapped in
a syntactically invalid way.

-onlyContents omits the outermost open and close tag, returning only the
serialized child nodes (like innerHTML property in a browser).  This allows
HTML fragments to be generated without having to process the result to strip
off the dummy document element wrapper.
…rror, don't add the node or set the result to the nodecmd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant