Async messaging framework still escapes string marked as safe

[Lin Hua Cheng]

The asycnhronous messaging framework still escapes string marked as safe (example: mark_safe("xxx")

Example code:

from django.utils.safestring import mark_safe
from horizon import messages
...
    msg = mark_safe("Operation succeeds, to view the record click on <a href="some URL">here</a>")
    messages.success(request, msg)
...

I think the messaging framework should check for mark_safe string to be consistent with the behavior of messaging framework of django.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/21257

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/21257
Committed: http://github.com/openstack/horizon/commit/43e8ea4d4d1967f82cfdb3b2a890fd5c40e84f6e
Submitter: Jenkins
Branch: master

commit 43e8ea4d4d1967f82cfdb3b2a890fd5c40e84f6e
Author: Lin Hua Cheng <email address hidden>
Date: Tue Feb 5 14:45:47 2013 -0800

    Fix on async messaging to don't escape message string marked as safe.

    Fixes bug 1103243.

    Change-Id: Ia9541d5cc338914f5f9164e7ee1386270211f4d0