Thanks for the explanation, Herwig.
I've tried to read up on (nested) browsing contexts stuff.
The best I found so far is
"http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#nested-browsing-context";
… which is still pretty dense - if anyone has a pointer to a more practica
The page in the iframe contains the REPL implementation for the browser.
It's compiled and optimized with its dependencies.
Therefore the client runs in its own window object, isolated from problems
including global identifiers, modified prototypes, differing library
versions and compilation modes.
David mentioned in another thread that "… the file that's meant to be loaded
into the cross page iframe…"
I noticed that before, but it always puzzled me - time to ask the Q.
Could someone please explain why the REPL downloads essentially the same
js-code when it connects as the js-code that ca
