diff --git a/src/Umbraco.Web.UI.Client/src/views/propertyeditors/rte/rte.controller.js b/src/Umbraco.Web.UI.Client/src/views/propertyeditors/rte/rte.controller.js
index f6cacfaf1f..89c3e2b264 100644
--- a/src/Umbraco.Web.UI.Client/src/views/propertyeditors/rte/rte.controller.js
+++ b/src/Umbraco.Web.UI.Client/src/views/propertyeditors/rte/rte.controller.js
@@ -34,7 +34,7 @@ angular.module("umbraco")
 
             //These are absolutely required in order for the macros to render inline
             //we put these as extended elements because they get merged on top of the normal allowed elements by tiny mce
-            var extendedValidElements = "@[id|class|style],-div[id|dir|class|align|style],ins[datetime|cite],-ul[class|style],-li[class|style], span[id|class|style]";
+            var extendedValidElements = "@[id|class|style],-div[id|dir|class|align|style],ins[datetime|cite],-ul[class|style],-li[class|style],span[id|class|style]";
 
             var invalidElements = tinyMceConfig.inValidElements;
             var plugins = _.map(tinyMceConfig.plugins, function (plugin) {
@@ -125,7 +125,7 @@ angular.module("umbraco")
 
                 if (tinyMceConfig.customConfig) {
 
-                    //if there is some custom config, we need to see if the string value of each item might actually be json and if so, we need to 
+                    //if there is some custom config, we need to see if the string value of each item might actually be json and if so, we need to
                     // convert it to json instead of having it as a string since this is what tinymce requires
                     for (var i in tinyMceConfig.customConfig) {
                         var val = tinyMceConfig.customConfig[i];
@@ -134,7 +134,7 @@ angular.module("umbraco")
                             if (val.detectIsJson()) {
                                 try {
                                     tinyMceConfig.customConfig[i] = JSON.parse(val);
-                                    //now we need to check if this custom config key is defined in our baseline, if it is we don't want to 
+                                    //now we need to check if this custom config key is defined in our baseline, if it is we don't want to
                                     //overwrite the baseline config item if it is an array, we want to concat the items in the array, otherwise
                                     //if it's an object it will overwrite the baseline
                                     if (angular.isArray(baseLineConfigObj[i]) && angular.isArray(tinyMceConfig.customConfig[i])) {
@@ -144,7 +144,7 @@ angular.module("umbraco")
                                 }
                                 catch (e) {
                                     //cannot parse, we'll just leave it
-                                } 
+                                }
                             }
                         }
                     }
@@ -164,13 +164,13 @@ angular.module("umbraco")
                         editor.getBody().setAttribute('spellcheck', true);
                     });
 
-                    //We need to listen on multiple things here because of the nature of tinymce, it doesn't 
+                    //We need to listen on multiple things here because of the nature of tinymce, it doesn't
                     //fire events when you think!
                     //The change event doesn't fire when content changes, only when cursor points are changed and undo points
-                    //are created. the blur event doesn't fire if you insert content into the editor with a button and then 
-                    //press save. 
-                    //We have a couple of options, one is to do a set timeout and check for isDirty on the editor, or we can 
-                    //listen to both change and blur and also on our own 'saving' event. I think this will be best because a 
+                    //are created. the blur event doesn't fire if you insert content into the editor with a button and then
+                    //press save.
+                    //We have a couple of options, one is to do a set timeout and check for isDirty on the editor, or we can
+                    //listen to both change and blur and also on our own 'saving' event. I think this will be best because a
                     //timer might end up using unwanted cpu and we'd still have to listen to our saving event in case they clicked
                     //save before the timeout elapsed.
 
@@ -190,7 +190,7 @@ angular.module("umbraco")
                     //            currForm.$setDirty();
                     //            alreadyDirty = true;
                     //        }
-                            
+
                     //    });
                     //});
 
@@ -225,7 +225,7 @@ angular.module("umbraco")
                         var srcAttr = $(e.target).attr("src");
                         var path = srcAttr.split("?")[0];
                         $(e.target).attr("data-mce-src", path + qs);
-                        
+
                         syncContent(editor);
                     });
 
@@ -336,7 +336,7 @@ angular.module("umbraco")
                 });
 
                 //when the element is disposed we need to unsubscribe!
-                // NOTE: this is very important otherwise if this is part of a modal, the listener still exists because the dom 
+                // NOTE: this is very important otherwise if this is part of a modal, the listener still exists because the dom
                 // element might still be there even after the modal has been hidden.
                 $scope.$on('$destroy', function () {
                     unsubscribe();