#24469: forms, form fields and media are escaped wrongfully in non django
templates
-------------------------------------+-------------------------------------
Reporter: MoritzS | Owner: aaugustin
Type: Bug | Status: assigned
Component: Template system | Version: 1.8beta2
Severity: Release blocker | Resolution:
Keywords: forms fields media | Triage Stage: Ready for
escape template jinja2 | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
I'm fine with the patch as is. Let's commit it rather than delay RC1.
Like I said on IRC, generally speaking, I'm wondering if adding this
`__html__` method on a case by case basis to some classes is the best idea
in the long run.
Can we identify every class whose `__str__` method returns a `SafeStr`? If
there's three of them, perhaps the ad-hoc method is fine. If there's
seventeen, then it's a different story.
Turning it into a mixin wouldn't save much code, would add a layer of
indirection and a small overhead, but it would also allow us to provide a
docstring.
--
Ticket URL: <https://code.djangoproject.com/ticket/24469#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.7383e735f89abf7ff212089191c99ab2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
