I was notified via Twitter the following by @ChristianSonne who worked on Bespin integration with Ubiquity. @ryansnyder First(?) bug for you - it is unsafe to have Bespin load content from div, when content is likely to contain html (like </div>) @ryansnyder http://tinyurl.com/yfgc3u7 and http://tinyurl.com/ylj385r is how we do it in Ubiquity - faced the same bug at first...
@ChristianSonne also mentioned that the issue was brought up in the Google Group: Noticed the problem after this msg to groups http://groups.google.com/group/mozilla-labs-jetpack/browse_thread/thread/575aba497cf4b9cb
Worked with morgamic to remove the Bespin editor temporarily. Now is a textarea. Tested and pushed to production. Should be reimplemented as Bespin, but not worried about that at the moment.
Fix the Bespin editor implementation and put back in edit jetpack page.
I'm still seeing tags being ripped out from my code. See: http://jetpackgallery.mozillalabs.com/jetpacks/312/code Notice the JS and CSS in CDATA blocks. These should wrapped in script and style tags respectively, but when I save they are removed, rendering the Jetpack useless.
Ok something I did made it magically work, but I am not sure what! I'll keep an eye out for further anomalies.
Per Daniel - We are holding off on Bespin integration.
Closing as wont fix; shutting down Jetpack Gallery at the end of the month and redirecting all traffic to addons.mozilla.org.