
12 Aug
2013
12 Aug
'13
2:51 a.m.
Trent W. Buck <trentbuck@gmail.com> wrote:
It's really a pity that edbrowse is too weird for js-happy web apps to work in it :-( Somebody said it was because it doesn't implement the DOM, which I didn't really understand.
Many Web applications manipulate the DOM tree, so yes, its lack of support for the DOM rules out Edbrowse for many script-dependent sites. I'm assuming you know what the DOM does: its an API for querying and modifying the document as a tree of objects, including CSS styles as well as HTML or XML elements. Beyond that there's the Window object, XMLHttpRequest, and many other APIs (e.g., the HTML DOM as defined now in HTML 5), persistent storage, and on and upward.