mirror of
https://github.com/ezyang/htmlpurifier.git
synced 2024-11-13 00:38:42 +00:00
aa0fdeee30
By default, the DirectLex and DOMLex behavior with stray angled brackets varied a great deal due to their implementations. A little known directive %Core.AggressivelyFixLt attempted to match DOMLex's behavior with DirectLex's, but it was off by default. By turning it on by default, users now enjoy these benefits, and performance-minded users can turn it back off. Also, several refinements to stray angled bracket parsing was made. Specifically: * DirectLex: Handle each left angled bracket individually, which prevents strange behavior as reported by eon. * DOMLex: Iterate aggressive lt fix, so that stacked brackets like << are handled. Signed-off-by: Edward Z. Yang <edwardzyang@thewritingpot.com>
17 lines
638 B
Plaintext
17 lines
638 B
Plaintext
Core.AggressivelyFixLt
|
|
TYPE: bool
|
|
VERSION: 2.1.0
|
|
DEFAULT: true
|
|
--DESCRIPTION--
|
|
<p>
|
|
This directive enables aggressive pre-filter fixes HTML Purifier can
|
|
perform in order to ensure that open angled-brackets do not get killed
|
|
during parsing stage. Enabling this will result in two preg_replace_callback
|
|
calls and at least two preg_replace calls for every HTML document parsed;
|
|
if your users make very well-formed HTML, you can set this directive false.
|
|
This has no effect when DirectLex is used.
|
|
</p>
|
|
<p>
|
|
<strong>Notice:</strong> This directive's default turned from false to true
|
|
in HTML Purifier 3.1.2.
|
|
</p> |