Questions on contributing new Docsets about dash-user-contributions HOT 6 CLOSED

The versioning guidelines are for the docset.json. You can name the folders in the versions folders however you want. In the example you gave, I'd recommend you name the folder just 2.0.7.

If you have the version set to 2.0.7/2014-03-26 it means that Dash will only display 2.0.7 to the user (the 2014-03-26 will never be shown). If later on you update the docset and set the version to something like 2.0.7/2014-05-01, Dash will update to your new docset, but the version displayed to the user will still be 2.0.7.

Dash should work fine with iframes. Have you tried enabling JavaScript for your docset? See http://kapeli.com/docsets#enableJavascript. If it still doesn't work after enabling JavaScript, please upload the docset somewhere and I'll check it out.

from dash-user-contributions.

OK, thanks for the clarity on the docset.json stuff. I'll keep that mind.

I double-checked the Info.plist file and it looks like I have the correct key and value for JavaScript. I also confirmed that JS works on some of the examples, but the iframe contents don't appear to load for one in particular. I got the other ones working by changing some of my generation code.

docset: http://cl.ly/1D0l1u3Z3w0s

• Working examples (using other HTML files from the docset): can.Control.route, function ☞ map (or you can find this one by searching for "map" and the page is called can.route.map)
• Broken Example (using JSFiddle link): can.Control

If it's a matter of that latter example being an external iframe, let me know. Most of our examples are like the first two working ones.

from dash-user-contributions.

The broken example doesn't work in Google Chrome or Safari either, so ... no idea. Maybe iframes inside local files is something JSFiddle doesn't allow?

from dash-user-contributions.

Very odd. I was able to see it working by loading the local file in my safari and chrome like so http://cl.ly/image/281J1R383K2j & http://cl.ly/image/3C2s2d0Y0Q2z. I'm inclined to ignore the problem with that tho, as I think I should actually re-write this one example to be like the others for consistency and control. And the "Edit in JSFiddle" link is there as a fallback at least...

Thanks for the quick follow up!

from dash-user-contributions.

Oh right sorry, it works in Chrome/Safari. I'll investigate what happens on Dash's end later today.

from dash-user-contributions.

I looked into it and as far as I can tell it happens because Dash blocks jsfiddle's Google Analytics request (jsfiddle stops loading after that). Dash blocks this because most docs include Google Analytics even in their offline version and if I'd let the request through the docs wouldn't really be 100% offline and would have issues on slow connections.

I tried to fix it by allowing these requests when they originate from inside an iframe that's already online, but I couldn't find a reliable way to determine this.

Since you said you're inclined to ignore this problem, I'm inclined to do that as well and let this bug live and be happy.

from dash-user-contributions.