After the recent meeting I proposed to create an API on both sides - MDN and jsFiddle. 1. MDN would provide it's own way of showing the examples (similar to http://mootools.net/demos/?demo=Chaining) 2. MDN would send the data needed to recreate an example in jsFiddle together with a unique, temporary hash identifying the editing request. 3. jsFiddle would display the example and provide a way to send the edited code back to MDN We agreed that this solution is removing quite a few issues as jsFiddle is not used for storage and MDN is safe from eventual jsFiddle outage. It is gonna be used only as an editor for examples. JsFiddle will need to provide an API similar to its current "POST API" http://doc.jsfiddle.net/api/post.html with some special abilities. MDN will need to create a wiki plugin to render code in an iframe served from a separate domain and ability to save data received from jsFiddle.
I'm going to say that the research for this is "done", as represented as action items in bug 797479 and bug 797483. We also have merged PRs for bug 797480, bug 797474, and bug 797472 which lay the groundwork for live samples in general.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.