HTMLPurifier_HTMLModule_Scripting Class Reference

Inheritance diagram for HTMLPurifier_HTMLModule_Scripting:

Collaboration diagram for HTMLPurifier_HTMLModule_Scripting:

Public Member Functions
	setup ($config)
Data Fields
	$name = 'Scripting'
	$elements = array('script', 'noscript')
	$content_sets = array('Block' => 'script | noscript', 'Inline' => 'script | noscript')
	$safe = false

---

Detailed Description

XHTML 1.1 Scripting module, defines elements that are used to contain information pertaining to executable scripts or the lack of support for executable scripts.

Note:

This module does not contain inline scripting elements

Definition at line 16 of file Scripting.php.

---

Member Function Documentation

setup

(

$

config

)

Lazy load construction of the module after determining whether or not it's needed, and also when a finalized configuration object is available.

Parameters:

$config

Instance of HTMLPurifier_Config

Reimplemented from HTMLPurifier_HTMLModule.

Definition at line 23 of file Scripting.php.

Here is the call graph for this function:

---

Field Documentation

$content_sets = array('Block' => 'script | noscript', 'Inline' => 'script | noscript')

Associative array of content set names to content set additions. This is commonly used to, say, add an A element to the Inline content set. This corresponds to an internal variable $content_sets and NOT info_content_sets member variable of HTMLDefinition.

Reimplemented from HTMLPurifier_HTMLModule.

Definition at line 20 of file Scripting.php.

$elements = array('script', 'noscript')

Informally, a list of elements this module changes. Not used in any significant way.

Reimplemented from HTMLPurifier_HTMLModule.

Definition at line 19 of file Scripting.php.

$name = 'Scripting'

Short unique string identifier of the module

Reimplemented from HTMLPurifier_HTMLModule.

Definition at line 18 of file Scripting.php.

$safe = false

Boolean flag whether or not this module is safe. If it is not safe, all of its members are unsafe. Modules are safe by default (this might be slightly dangerous, but it doesn't make much sense to force HTML Purifier, which is based off of safe HTML, to explicitly say, "This is safe," even though there are modules which are "unsafe")

Note:

Previously, safety could be applied at an element level granularity. We've removed this ability, so in order to add "unsafe" elements or attributes, a dedicated module with this property set to false must be used.

Reimplemented from HTMLPurifier_HTMLModule.

Definition at line 21 of file Scripting.php.

---

The documentation for this class was generated from the following file:

• C:/xampp/htdocs/moodle/lib/htmlpurifier/HTMLPurifier/HTMLModule/Scripting.php