HTMLPurifier_Node
in package
Abstract base node class that all others inherit from.
Why do we not use the DOM extension? (1) It is not always available, (2) it has funny constraints on the data it can represent, whereas we want a maximally flexible representation, and (3) its interface is a bit cumbersome.
Table of Contents
Properties
- $armor : mixed
- Lookup array of processing that this token is exempt from.
- $col : mixed
- Column number of the start token in the source document. Null if unknown.
- $dead : mixed
- When true, this node should be ignored as non-existent.
- $line : mixed
- Line number of the start token in the source document
Methods
- toTokenPair() : mixed
- Returns a pair of start and end tokens, where the end token is null if it is not necessary. Does not include children.
Properties
$armor
Lookup array of processing that this token is exempt from.
public
mixed
$armor
= array()
Currently, valid values are "ValidateAttributes".
Tags
$col
Column number of the start token in the source document. Null if unknown.
public
mixed
$col
Tags
$dead
When true, this node should be ignored as non-existent.
public
mixed
$dead
= \false
Who is responsible for ignoring dead nodes? FixNesting is responsible for removing them before passing on to child validators.
$line
Line number of the start token in the source document
public
mixed
$line
Tags
Methods
toTokenPair()
Returns a pair of start and end tokens, where the end token is null if it is not necessary. Does not include children.
public
abstract toTokenPair() : mixed