Interface ParserOptions

If true then CDATA sections are recognized.

If true then processing instructions are recognized.

If true then self-closing tags are recognized, otherwise they are treated as start tags.

If true then ASCII alpha characters are case-insensitive in tag names.

If true then end tags that don't have a corresponding start tag are ignored. Otherwise, a ParserError is thrown.

Use in conjunctions with areUnbalancedStartTagsImplicitlyClosed.

<a></b></a> → <a></a>
   ^^^^ b is ignored
Copy

If true then unbalanced start tags are forcefully closed. Otherwise, a ParserError is thrown.

Use in conjunctions with areUnbalancedEndTagsIgnored.

<a><b></a>  →  <a><b></b></a>
                     ^^^^ b is implicitly closed
Copy

The map from a foreign tag name to a tokenizer options applied to the tag children.

The map from a tag (A) to a list of tags that must be closed if tag (A) is opened.

For example, in HTML p and h1 tags have the following semantics:

<p><h1>  →  <p></p><h1></h1>
               ^^^^ p is implicitly closed by h1
Copy

To achieve this behavior, set this option to:

// h1 implicitly closes p
{ h1: ['p'] }
Copy

Use in conjunctions with areUnbalancedStartTagsImplicitlyClosed.

The list of tags for which a start tag is inserted if an unbalanced end tag is met. Otherwise, a ParserError is thrown.

You can ignore unbalanced end tags with areUnbalancedEndTagsIgnored.

For example, in HTML p and br tags follow this semantics:

</p>   →  <p></p>
          ^^^ p is implicitly opened

</br>  →  <br/>
             ^ br is implicitly opened
Copy

To achieve this behavior, set this option to:

['p', 'br']
Copy

If true then tag names and attributes are processed with XML constraints.

The list of tags which content is interpreted as plain text.

The list of tags that can't have any contents (since there's no end tag, no content can be put between the start tag and the end tag).