aboutsummaryrefslogtreecommitdiffhomepage
path: root/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt
diff options
context:
space:
mode:
Diffstat (limited to 'inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt')
-rw-r--r--inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt11
1 files changed, 0 insertions, 11 deletions
diff --git a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt b/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt
deleted file mode 100644
index ed6f1342..00000000
--- a/inc/3rdparty/htmlpurifier/HTMLPurifier/ConfigSchema/schema/Core.RemoveProcessingInstructions.txt
+++ /dev/null
@@ -1,11 +0,0 @@
1Core.RemoveProcessingInstructions
2TYPE: bool
3VERSION: 4.2.0
4DEFAULT: false
5--DESCRIPTION--
6Instead of escaping processing instructions in the form <code>&lt;? ...
7?&gt;</code>, remove it out-right. This may be useful if the HTML
8you are validating contains XML processing instruction gunk, however,
9it can also be user-unfriendly for people attempting to post PHP
10snippets.
11--# vim: et sw=4 sts=4