#10449: HTML accents not escaped out when using forms
-------------------------------------+-------------------------------------
Reporter: tipan | Owner: Abhishek
| Mane
Type: Bug | Status: assigned
Component: | Version: 1.0
Internationalization |
Severity: Normal | Resolution:
Keywords: accents, newforms | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Abhishek Mane):
* has_patch: 0 => 1
* needs_tests: 1 => 0
* owner: nobody => Abhishek Mane
* status: new => assigned
Comment:
I investigated this issue and found that modern Django's template-based
widget rendering no longer suffers from this double-escaping bug, provided
the translated strings are explicitly marked as safe. >
I have submitted a PR that adds a regression test to test_select.py to
prove mark_safe correctly prevents double-escaping in Select choices. This
fulfills the "Needs tests" requirement and proves the bug is resolved so
this ticket can finally be closed:
[https://github.com/django/django/pull/20871]
--
Ticket URL: <https://code.djangoproject.com/ticket/10449#comment:19>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019ccd6b061a-fe609b28-d133-4fa6-bcfe-2e38d79c395f-000000%40eu-central-1.amazonses.com.