This one is a pain, it either requires you to build a HTTPS service on your machine which points to the directory that the SASS is compiled from or you need to adjust browser settings to add an exception to allow mixed content.
We're not using HTTPS on our staging environment at the moment but I have played around with running a HTTPS server from my machine for testing, this is one of the areas that Lithium will need to address as more and more communities switch over to HTTPS default traffic.
For Chrome the following should work in terminal to allow mixed-content mode:
open /Applications/Google\ Chrome.app --args --allow-running-insecure-content
Ah that did it! Nice :) thanks for your help with this. I am always learning something new with this platform.
I also agree with the http/https configuration stuff. It would make sense for the SDK to serve up a https version (or at the very least base the protocol on the staging url provided). I may have more questions after having a play around :)
