Just for the record, templates that are inserted “inline” must be well formed XML. This means, amongst other things: the 5 XML special characters (< > ’ " & ) must be escaped, and there must be a single root node (in your case the <div> tag)
Is there any way to prevent the user from entering a not properly formated xml text? I guess this ties into my other question in regards to preventing the end user from entering certain characters?
Will it work if you enclose for example some javascript in <![CDATA[ … ]]?
It should then be valid xml and not need escaping
I have a snippet that uses some javascript it all works fine when used in a page but when inserted in to ephox inline the search window just hangs with Your request is being processed. Please wait a moment…
I’ve successfully managed to insert Javascript code (just tested with alert(‘foo’) in the editlive box (surround the actual code with CDATA), and it works on preview (ie. the javascript runs), however on publish, this code doesn’t run…never bothered to figure out precisely why as I got caught up in other matters. Would be curious to know if anyone else has tried this (or has managed to disable this “feature”)