[github/wallabag/wallabag.git] / inc / 3rdparty / htmlpurifier / HTMLPurifier / ConfigSchema / schema / HTML.ForbiddenElements.txt

HTML.ForbiddenElements\r
TYPE: lookup\r
VERSION: 3.1.0\r
DEFAULT: array()\r
--DESCRIPTION--\r
<p>\r
    This was, perhaps, the most requested feature ever in HTML\r
    Purifier. Please don't abuse it! This is the logical inverse of\r
    %HTML.AllowedElements, and it will override that directive, or any\r
    other directive.\r
</p>\r
<p>\r
    If possible, %HTML.Allowed is recommended over this directive, because it\r
    can sometimes be difficult to tell whether or not you've forbidden all of\r
    the behavior you would like to disallow. If you forbid <code>img</code>\r
    with the expectation of preventing images on your site, you'll be in for\r
    a nasty surprise when people start using the <code>background-image</code>\r
    CSS property.\r
</p>\r
--# vim: et sw=4 sts=4\r
Commit	Line	Data
d4949327 NL	1	HTML.ForbiddenElements\r
	2	TYPE: lookup\r
	3	VERSION: 3.1.0\r
	4	DEFAULT: array()\r
	5	--DESCRIPTION--\r
	6	<p>\r
	7	This was, perhaps, the most requested feature ever in HTML\r
	8	Purifier. Please don't abuse it! This is the logical inverse of\r
	9	%HTML.AllowedElements, and it will override that directive, or any\r
	10	other directive.\r
	11	</p>\r
	12	<p>\r
	13	If possible, %HTML.Allowed is recommended over this directive, because it\r
	14	can sometimes be difficult to tell whether or not you've forbidden all of\r
	15	the behavior you would like to disallow. If you forbid <code>img</code>\r
	16	with the expectation of preventing images on your site, you'll be in for\r
	17	a nasty surprise when people start using the <code>background-image</code>\r
	18	CSS property.\r
	19	</p>\r
	20	--# vim: et sw=4 sts=4\r