diff options
author | Bernhard Posselt <dev@bernhard-posselt.com> | 2014-10-21 22:53:36 +0200 |
---|---|---|
committer | Bernhard Posselt <dev@bernhard-posselt.com> | 2014-10-21 22:53:36 +0200 |
commit | fe030e7339f5fc9ec4e75d9655b2ced0900da5c2 (patch) | |
tree | d87fc2bc4504392550c3aea0abb18614d36f8abb /3rdparty/htmlpurifier/WYSIWYG | |
parent | 8c2a1b242c1cd2f7bcb179facc524f3454e7a863 (diff) |
use composer for autoloading repos
Diffstat (limited to '3rdparty/htmlpurifier/WYSIWYG')
-rw-r--r-- | 3rdparty/htmlpurifier/WYSIWYG | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/3rdparty/htmlpurifier/WYSIWYG b/3rdparty/htmlpurifier/WYSIWYG deleted file mode 100644 index c518aacdd..000000000 --- a/3rdparty/htmlpurifier/WYSIWYG +++ /dev/null @@ -1,20 +0,0 @@ - -WYSIWYG - What You See Is What You Get - HTML Purifier: A Pretty Good Fit for TinyMCE and FCKeditor - -Javascript-based WYSIWYG editors, simply stated, are quite amazing. But I've -always been wary about using them due to security issues: they handle the -client-side magic, but once you've been served a piping hot load of unfiltered -HTML, what should be done then? In some situations, you can serve it uncleaned, -since you only offer these facilities to trusted(?) authors. - -Unfortunantely, for blog comments and anonymous input, BBCode, Textile and -other markup languages still reign supreme. Put simply: filtering HTML is -hard work, and these WYSIWYG authors don't offer anything to alleviate that -trouble. Therein lies the solution: - -HTML Purifier is perfect for filtering pure-HTML input from WYSIWYG editors. - -Enough said. - - vim: et sw=4 sts=4 |