mirror of
https://github.com/django/django.git
synced 2025-12-04 00:55:36 +00:00
Fixed #24046 -- Deprecated the "escape" half of utils.safestring.
This commit is contained in:
parent
c3e1086949
commit
2f0e0eee45
13 changed files with 87 additions and 20 deletions
|
|
@ -210,15 +210,6 @@ passed around inside the template code:
|
|||
# Do something with the "safe" string.
|
||||
...
|
||||
|
||||
* **Strings marked as "needing escaping"** are *always* escaped on
|
||||
output, regardless of whether they are in an :ttag:`autoescape` block or
|
||||
not. These strings are only escaped once, however, even if auto-escaping
|
||||
applies.
|
||||
|
||||
Internally, these strings are of type ``EscapeBytes`` or
|
||||
``EscapeText``. Generally you don't have to worry about these; they
|
||||
exist for the implementation of the :tfilter:`escape` filter.
|
||||
|
||||
Template filter code falls into one of two situations:
|
||||
|
||||
1. Your filter does not introduce any HTML-unsafe characters (``<``, ``>``,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue