Code

Opened 5 years ago

Closed 5 years ago

#10409 closed (invalid)

join filter escapes data

Reported by: lorien Owned by: nobody
Component: Template system Version: master
Severity: Keywords: filter, join, escaping, safe
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

django rev. 9962

In [11]: Template('{{ messages|join:" "|safe }}').render(Context({'messages': ['<a>', '<b>']}))
Out[11]: u'&lt;a&gt; &lt;b&gt;'

Is it correct behaviour?

Attachments (0)

Change History (1)

comment:1 Changed 5 years ago by kmtracey

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

django-users would have been a better place for this, as it is a question. If you are not sure it is a bug, ask on the list first. The behavior is correct, see #9700. Also, you may want to look at the safeseq filter added for #9701.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.