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