Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs fixes for Bug 298827: builtin or built-in and Bug 298832: ie (sp)

Browse Source 
Patch by Frank Wein <bugzilla@mcsmurf.de>, r=me


git-svn-id: svn://10.0.0.236/trunk@249348 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
mozilla%colinogilvie.co.uk 2008-04-04 06:52:00 +00:00
parent a5f96dfdcf
commit b51adcbaf3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
mozilla/webtools/bugzilla/docs/en/xml/customization.xml
View File

@ -153,7 +153,7 @@
to properly HTML filter data that has been passed into the template.
This means that if the data can possibly contain special HTML characters
such as &lt;, and the data was not intended to be HTML, they need to be
converted to entity form, ie &amp;lt;. You use the 'html' filter in the
converted to entity form, i.e. &amp;lt;. You use the 'html' filter in the
Template Toolkit to do this. If you forget, you may open up
your installation to cross-site scripting attacks.
</para>
@ -162,7 +162,7 @@
Also note that Bugzilla adds a few filters of its own, that are not
in standard Template Toolkit. In particular, the 'url_quote' filter
can convert characters that are illegal or have special meaning in URLs,
such as &amp;, to the encoded form, ie %26. This actually encodes most
such as &amp;, to the encoded form, i.e. %26. This actually encodes most
characters (but not the common ones such as letters and numbers and so
on), including the HTML-special characters, so there's never a need to
HTML filter afterwards.