From 32bdf42913518b3421986cb4d49d62ed1b04354e Mon Sep 17 00:00:00 2001 From: Mario Vavti Date: Sat, 22 Aug 2020 19:50:15 +0200 Subject: composer update htmlpurifier --- vendor/ezyang/htmlpurifier/WYSIWYG | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 vendor/ezyang/htmlpurifier/WYSIWYG (limited to 'vendor/ezyang/htmlpurifier/WYSIWYG') diff --git a/vendor/ezyang/htmlpurifier/WYSIWYG b/vendor/ezyang/htmlpurifier/WYSIWYG deleted file mode 100644 index c518aacdd..000000000 --- a/vendor/ezyang/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 -- cgit v1.2.3