Use field_is_html flags in GravatarConsentRequirement
Review Request #9967 — Created May 23, 2018 and discarded — Latest diff uploaded
Instead of using
mark_safedirectly, we now set the{field}_is_html
flag so that it will be rendered as HTML. This also corrects the issue
that theintent_descriptionwas being marked as safe immediately
after callingugettext_lazy, which would result in the stored
attribute not being translated for users (as it already would have been
forced to go through the translation step by callingmark_safe).
Viewed the consent requirements page and saw the HTML was rendered
correctly.