2TYPE: bool
3VERSION: 3.2.0
4DEFAULT: false
7  When enabled, HTML Purifier will attempt to remove empty elements that
8  contribute no semantic information to the document. The following types
9  of nodes will be removed:
12    Tags with no attributes and no content, and that are not empty
13    elements (remove <code>&lt;a&gt;&lt;/a&gt;</code> but not
14    <code>&lt;br /&gt;</code>), and
15  </li>
16  <li>
17    Tags with no content, except for:<ul>
18      <li>The <code>colgroup</code> element, or</li>
19      <li>
20        Elements with the <code>id</code> or <code>name</code> attribute,
21        when those attributes are permitted on those elements.
22      </li>
23    </ul></li>
26  Please be very careful when using this functionality; while it may not
27  seem that empty elements contain useful information, they can alter the
28  layout of a document given appropriate styling. This directive is most
29  useful when you are processing machine-generated HTML, please avoid using
30  it on regular user HTML.
33  Elements that contain only whitespace will be treated as empty. Non-breaking
34  spaces, however, do not count as whitespace. See
35  %AutoFormat.RemoveEmpty.RemoveNbsp for alternate behavior.
38  This algorithm is not perfect; you may still notice some empty tags,
39  particularly if a node had elements, but those elements were later removed
40  because they were not permitted in that context, or tags that, after
41  being auto-closed by another tag, where empty. This is for safety reasons
42  to prevent clever code from breaking validation. The general rule of thumb:
43  if a tag looked empty on the way in, it will get removed; if HTML Purifier
44  made it empty, it will stay.
46--# vim: et sw=4 sts=4