#23831: mark_safe and mark_for_escaping should account for __html__
-------------------------------------+------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+------------------------
The changes made #7261 aren't complete. They made it possible for other
libraries to interpret strings marked explicitly as safe or unsafe in
Django. However Django doesn't always interpret correctly strings marked
by other libraries.
The reason is that mark_safe and mark_for_escaping don't account for
`__html__`. As a consequence escaping information is lost once these
functions get called, and they're called in many places.
Thanks mitsuhiko for the report.
--
Ticket URL: <https://code.djangoproject.com/ticket/23831>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.291bbe118e804b9af1fdd954758bc659%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
