Handle limited-HTML fields

RESOLVED FIXED in 5.8

Status

addons.mozilla.org Graveyard
Public Pages
P3
normal
RESOLVED FIXED
8 years ago
2 years ago

People

(Reporter: jbalogh, Assigned: jbalogh)

Tracking

Details

(Whiteboard: [z])

(Assignee)

Description

8 years ago
We're allowing HTML in some fields these days, so we need to prevent extra escaping on those.  Creating some kind of HtmlField that subclasses TranslatedField might be a good way to go about this.  If your __unicode__ method returns a jinja2.Markup object, jinja won't try to escape it.

I think the HTML cleanup (bug 543019) can happen in HtmlField's save method.
Assignee: nobody → jbalogh
Priority: -- → P3
(Assignee)

Updated

8 years ago
Target Milestone: 5.7 → 5.8
(Assignee)

Comment 1

8 years ago
http://github.com/jbalogh/zamboni/commit/10540584073a7e8b485c1d3db2402e9c205d569e

Now we have PurifiedField and LinkifiedField.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.