[Edbrowse-dev] XMLHttpRequest

[Karl Dahlke <eklhad@comcast.net>]

Since almost the dawn of html, <frame> and <iframe> can cause a browser
to fetch other html, perhaps from another domain, and paste the result into the web page.
In this regard edbrowse is more manual than any other browser; you have to click on a link to fetch in the frame.
Not saying I like it that way, I don't, it was just easier at the time.
Anyways other browsers just do it, without worrying about security,
I don't think XMLHttpRequest is any different; except js is directing the http fetch,
and perhaps using the result in some computational way,
rather than html directing the fetch and browsing the result.
Most of the time even js just slaps the html into a <div> where it is browsed;
just a damn fancy complicated, and dynamic, form of iframe.
I'd be surprised if a js fetch had to draw from the same domain, but it might, IDK.
Maybe write some test code and run it on other browsers.

By the way, we should think about expanding all these frames and iframes, as other browsers do,
but it's more work than first appears.
The top half of your "buffer" is this tree from this html on this domain running this instance of js,
and the bottom half of your buffer is that tree from that html on that domain running that instance of js,
so multiple js windows tied to one edbrowse window, which we can't do now, etc etc.
definitely some work there; for now an improved dom and jquery is more important.

Karl Dahlke