From 1f0fc9d26fed8ea7b3d035b1473acf5abb448a8b Mon Sep 17 00:00:00 2001
From: Chris Hill-Scott <me@quis.cc>
Date: Tue, 28 Feb 2017 17:02:09 +0000
Subject: [PATCH] Fix errant &nbsp; on request to go live page
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

There’s a good reason for having the `&nbsp;` – it stops GOV.UK Notify
being split across two lines (which could happen on a smaller viewport,
eg mobile). Gotta protect the brand.

Not good for the brand for it to be showing up in the page though 😬

This got broken as part of 3f41090a9428934bef480baceb07b4eae8a84fd4

The label for a form should never have user-submitted content in it, so
using `safe` is fine.
---
 app/templates/components/radios.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/templates/components/radios.html b/app/templates/components/radios.html
index 946dff22b..1828a5222 100644
--- a/app/templates/components/radios.html
+++ b/app/templates/components/radios.html
@@ -7,7 +7,7 @@
   <div class="form-group {% if field.errors %} error{% endif %}">
     <fieldset>
       <legend class="form-label">
-        {{ field.label.text }}
+        {{ field.label.text|safe }}
         {% if field.errors %}
           <span class="error-message">
             {{ field.errors[0] }}