tag:blogger.com,1999:blog-1018631932325841015.post6016578939996494976..comments2014-04-01T12:42:22.883-04:00Comments on Ember Noob: Ember.js Debugging 1 — FirefoxOfer Navehttp://www.blogger.com/profile/02310584127036218839noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1018631932325841015.post-48863893398574018012012-10-05T14:59:26.567-04:002012-10-05T14:59:26.567-04:00Great tip! I just tried it, and since I'm usi...Great tip! I just tried it, and since I'm using a public fiddle under my account (one with a title), the url includes my username, so it ended up being http://fiddle.jshell.net/odigity/whhpN/show/.<br /><br />But then I tried just adding 'show/' to the original URL, and that worked, too: http://jsfiddle.net/odigity/whhpN/show/<br /><br />I just learned about another alternative last night while re-watching Tom Dale's Debugging Ember presentation to prepare for my next debugging post (http://vimeo.com/37539737). If you're using Chrome's Web Developer Tools, there's a select box at the bottom that lets you pick with frame in the current page to use as your console context, so you can pick the show frame that way.Ofer Navehttps://www.blogger.com/profile/02310584127036218839noreply@blogger.comtag:blogger.com,1999:blog-1018631932325841015.post-27131948962201974702012-10-05T10:34:44.350-04:002012-10-05T10:34:44.350-04:00The reason that you can't interact with your o...The reason that you can't interact with your output in jsFiddle is because its intentionally sandboxed for security (it uses fiddle.jshell.net instead of just jsfiddle.net). However, there is a pretty simple work-around for this. Just open the output iframe in a new window/tab instead of having it as an iframe. So, if your URL is http://jsfiddle.net/xyz/ then try http://fiddle.jshell.net/xyz/show/ (see also http://doc.jsfiddle.net/use/embedding.html)iX3https://www.blogger.com/profile/08331632914258692778noreply@blogger.com