> What do you think about trying to isolate the cause by going into the
> version control and compiling edbrowse from different moments in time, til
> you hone in on the point of transition where Raw Story or Washington Post
> did work before a patch and no longer worked after it?

I don't think it would tell us anything.
This problem popped up because we got enough of the js working to move forward, and make the links, whence one of those links does not make a proper tree.
Adam's removeAttribute for example, it works and the js moves forward.
(Speaking of which, I made all the Attribute routines consistent, and hopefully correct.)
It's like turning on the light and seeing the mess.
We wouldn't want to back up, we want to keep moving on.
Delve into a site and find out why that link doesn't assemble a proper tree -
or check the spec again and maybe it says somewhere that I'm suppose to unlink the node from where it was, if it was already in the tree, then put it in the new place.
db4 and watch all the nodes created from html, and dynamically, and how they put together.
Would be great if we had a site with no js errors, and still the tree problem, then we'd know we were on to something.
But these sites still have lots of js errors, lots of functions that don't run to completion, so who knows.
Maybe we could tell visually from another browser what the tree of nodes is suppose to be.

Karl Dahlke