Karl Dahlke <[email protected]> writes: > Forgive me I haven't looked at the code at all, > but I would guess there's a tidy5 encodeTags() that takes the > html text and makes the tree.
Essentially true. The details are a bit more complicated, but this is the idea. We call tidy to parse the html, and we get back a structure from tidy called a document. It contains our tree of nodes, and we can iterate over it. The problem is, this is a usable parse tree for the html, but it isn't a true DOM. We can remove nodes and attributes from the tree, but we can't add them. That causes problems for JS that needs to add new nodes. So we're going to have to take that parse tree we get back from Tidy5, build our own DOM out of it, and eventually render it. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
