aboutsummaryrefslogtreecommitdiffhomepage
path: root/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt
diff options
context:
space:
mode:
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt')
-rw-r--r--inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt18
1 files changed, 0 insertions, 18 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt
deleted file mode 100644
index e0fa378e..00000000
--- a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.AggressivelyFixLt.txt
+++ /dev/null
@@ -1,18 +0,0 @@
1Core.AggressivelyFixLt
2TYPE: bool
3VERSION: 2.1.0
4DEFAULT: true
5--DESCRIPTION--
6<p>
7 This directive enables aggressive pre-filter fixes HTML Purifier can
8 perform in order to ensure that open angled-brackets do not get killed
9 during parsing stage. Enabling this will result in two preg_replace_callback
10 calls and at least two preg_replace calls for every HTML document parsed;
11 if your users make very well-formed HTML, you can set this directive false.
12 This has no effect when DirectLex is used.
13</p>
14<p>
15 <strong>Notice:</strong> This directive's default turned from false to true
16 in HTML Purifier 3.2.0.
17</p>
18--# vim: et sw=4 sts=4