diff options
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt')
-rw-r--r-- | inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt new file mode 100644 index 00000000..40466c46 --- /dev/null +++ b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/HTML.ForbiddenElements.txt | |||
@@ -0,0 +1,20 @@ | |||
1 | HTML.ForbiddenElements | ||
2 | TYPE: lookup | ||
3 | VERSION: 3.1.0 | ||
4 | DEFAULT: array() | ||
5 | --DESCRIPTION-- | ||
6 | <p> | ||
7 | This was, perhaps, the most requested feature ever in HTML | ||
8 | Purifier. Please don't abuse it! This is the logical inverse of | ||
9 | %HTML.AllowedElements, and it will override that directive, or any | ||
10 | other directive. | ||
11 | </p> | ||
12 | <p> | ||
13 | If possible, %HTML.Allowed is recommended over this directive, because it | ||
14 | can sometimes be difficult to tell whether or not you've forbidden all of | ||
15 | the behavior you would like to disallow. If you forbid <code>img</code> | ||
16 | with the expectation of preventing images on your site, you'll be in for | ||
17 | a nasty surprise when people start using the <code>background-image</code> | ||
18 | CSS property. | ||
19 | </p> | ||
20 | --# vim: et sw=4 sts=4 | ||