Re: [Edbrowse-dev] js command line access

[Kevin Carhart <kevin@carhart.net>]

> In this case I don't really see the security argument.

Heh heh.  Oh, in that case.. great!  I was anticipating the worst.

> If it's there then not documenting it just means someone has to look at the

Well, it isn't there, it just lives offline in my divergent, obsolete 
3.3.1.
I wrote it before youall had done the lovely JS encapsulation work.
The early pleistocene relative to today!

This was my MO for a while - I would load a page, using the
wonderful auth-cookies-http edbrowse, and then once I was in JS land,
I wasn't re-rendering, I was just echoing things to learn
about the DOM from the inside out.  I had my work cut out
for me, without completing the circle back to edbrowse.
It's the innate temptation of open 
source that you can always diverge your own hybrid at any time and fool
around instead of making patches intended for the world.
It's both good and bad, because you go off on your own cul-de-sac
and it's harder to talk to the developers because you're out of
sync.  But I learned a bunch of JS and jquery which I anticipated
could eventually be brought back to the project, especially now
that we have a node tree from tidy!!

Kevin