[github/wallabag/wallabag.git] / inc / 3rdparty / htmlpurifier / HTMLPurifier / ConfigSchema / schema / Filter.ExtractStyleBlocks.Scope.txt

Filter.ExtractStyleBlocks.Scope\r
TYPE: string/null\r
VERSION: 3.0.0\r
DEFAULT: NULL\r
ALIASES: Filter.ExtractStyleBlocksScope, FilterParam.ExtractStyleBlocksScope\r
--DESCRIPTION--\r
\r
<p>\r
  If you would like users to be able to define external stylesheets, but\r
  only allow them to specify CSS declarations for a specific node and\r
  prevent them from fiddling with other elements, use this directive.\r
  It accepts any valid CSS selector, and will prepend this to any\r
  CSS declaration extracted from the document. For example, if this\r
  directive is set to <code>#user-content</code> and a user uses the\r
  selector <code>a:hover</code>, the final selector will be\r
  <code>#user-content a:hover</code>.\r
</p>\r
<p>\r
  The comma shorthand may be used; consider the above example, with\r
  <code>#user-content, #user-content2</code>, the final selector will\r
  be <code>#user-content a:hover, #user-content2 a:hover</code>.\r
</p>\r
<p>\r
  <strong>Warning:</strong> It is possible for users to bypass this measure\r
  using a naughty + selector. This is a bug in CSS Tidy 1.3, not HTML\r
  Purifier, and I am working to get it fixed. Until then, HTML Purifier\r
  performs a basic check to prevent this.\r
</p>\r
--# vim: et sw=4 sts=4\r
Commit	Line	Data
d4949327 NL	1	Filter.ExtractStyleBlocks.Scope\r
	2	TYPE: string/null\r
	3	VERSION: 3.0.0\r
	4	DEFAULT: NULL\r
	5	ALIASES: Filter.ExtractStyleBlocksScope, FilterParam.ExtractStyleBlocksScope\r
	6	--DESCRIPTION--\r
	7	\r
	8	<p>\r
	9	If you would like users to be able to define external stylesheets, but\r
	10	only allow them to specify CSS declarations for a specific node and\r
	11	prevent them from fiddling with other elements, use this directive.\r
	12	It accepts any valid CSS selector, and will prepend this to any\r
	13	CSS declaration extracted from the document. For example, if this\r
	14	directive is set to <code>#user-content</code> and a user uses the\r
	15	selector <code>a:hover</code>, the final selector will be\r
	16	<code>#user-content a:hover</code>.\r
	17	</p>\r
	18	<p>\r
	19	The comma shorthand may be used; consider the above example, with\r
	20	<code>#user-content, #user-content2</code>, the final selector will\r
	21	be <code>#user-content a:hover, #user-content2 a:hover</code>.\r
	22	</p>\r
	23	<p>\r
	24	<strong>Warning:</strong> It is possible for users to bypass this measure\r
	25	using a naughty + selector. This is a bug in CSS Tidy 1.3, not HTML\r
	26	Purifier, and I am working to get it fixed. Until then, HTML Purifier\r
	27	performs a basic check to prevent this.\r
	28	</p>\r
	29	--# vim: et sw=4 sts=4\r