\HTMLPurifier_Node_Element

Concrete element node class.

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.

Summary

Methods
Properties
Constants
toTokenPair()
__construct()
$line
$col
$armor
$dead
$name
$attr
$children
$empty
$endCol
$endLine
$endArmor
No constants found
No protected methods found
No protected properties found
N/A
No private methods found
No private properties found
N/A

Properties

$line

$line : 

Line number of the start token in the source document

Type

$col

$col : 

Column number of the start token in the source document. Null if unknown.

Type

$armor

$armor : 

Lookup array of processing that this token is exempt from.

Currently, valid values are "ValidateAttributes".

Type

$dead

$dead : 

When true, this node should be ignored as non-existent.

Who is responsible for ignoring dead nodes? FixNesting is responsible for removing them before passing on to child validators.

Type

$name

$name : 

The lower-case name of the tag, like 'a', 'b' or 'blockquote'.

Type

$attr

$attr : 

Associative array of the node's attributes.

Type

$children

$children : 

List of child elements.

Type

$empty

$empty : 

Does this use the <a></a> form or the </a> form, i.e.

is it a pair of start/end tokens or an empty token.

Type

$endCol

$endCol : 

Type

$endLine

$endLine : 

Type

$endArmor

$endArmor : 

Type

Methods

toTokenPair()

toTokenPair() 

Returns a pair of start and end tokens, where the end token is null if it is not necessary. Does not include children.

__construct()

__construct(  $name,   $attr = array(),   $line = null,   $col = null,   $armor = array()) 

Parameters

$name
$attr
$line
$col
$armor