All Implemented Interfaces:
LSSerializerFilters provide applications the ability to examine nodes as they are being serialized and decide what nodes should be serialized or not. The
LSSerializerFilterinterface is based on the
NodeFilterinterface defined in [DOM Level 2 Traversal and Range] .
, and children of
Attr nodes are not passed to the filter.
The child nodes of an
EntityReference node are only passed
to the filter if the
EntityReference node is skipped by the
When serializing an
Element, the element is passed to the
filter before any of its attributes are passed to the filter. Namespace
declaration attributes, and default attributes (except in the case when "
discard-default-content" is set to
false), are never passed
to the filter.
The result of any attempt to modify a node passed to a
LSSerializerFilter is implementation dependent.
DOM applications must not raise exceptions in a filter. The effect of throwing exceptions from a filter is DOM implementation dependent.
For efficiency, a node passed to the filter may not be the same as the one that is actually in the tree. And the actual node (node object identity) may be reused during the process of filtering and serializing a document.
|Method from org.w3c.dom.ls.LSSerializerFilter Summary:|
|Method from org.w3c.dom.ls.LSSerializerFilter Detail:|
public int getWhatToShow()
Unlike [DOM Level 2 Traversal and Range] , the
The constants used here are defined in [DOM Level 2 Traversal and Range] .