Closed gideonthomas closed 9 years ago
The problem starts with this commit which allows thimble to use brackets from another domain
Paging @sedge...is this just locally or upstream too? NOTE you need to update your .env locally to get the right domains.
https://github.com/sedge/thimble.webmaker.org/commit/b63ece9ec6287694ee65c05fe21e39c3e9d575ff#diff-bb503f3d9047bcd4a5730559f1e16560R36 should be made smarter to know about port details, too. Question, why are we doing this parsing at all? Why not have different configs for different scenarios?
Let's do different configs - one for the origin that serves bramble and another for where the submodule is being served from.
It's the difference between someorigin.com
and someorigin.com/subroute/[dist or src]
Who can work on this so we don't leave Thimble broken?
Reported by @KeniMorri and @K-LV is shown when we try to load thimble locally which uses whatevers on brackets:bramble
Seems like Thimble is not passing the "bramble:init" postMessage to brackets-browser-livedev which is why it never fulfils it's initExtension promise which is why it times out.