[Edbrowse-dev] Parallel versions of js access functions

[Karl Dahlke <eklhad@comcast.net>]

> The tags in the innerHTML could be inherently intermediate.

Yes they could, and in that case the side effects would
eventually create them and delete them,
or perhaps create them but never link them into the tree and thus never rendered.
That's not great but not awful,
and probably not worth all the software it would take
to detect and manage this situation.
Disconnected parts will all clean up during unbrowse
as part of garbage collection.
I'm inclined to just let it ride.

So very well, document.write will process via the same mechanism
as innerHTML, under the aegis of the innerHTML setter function
in native js, at the moment of execution.
The real trick is passing the created subtree back to edbrowse,
which I have some ideas on, that are not fully formed yet.
Once reconstituted on our side, the subtree can be pasted into our primary tree,
ready for rendering.

Karl Dahlke