Ok all, on every browse, tidy5 turns html into a tree, and I then render that tree into a readable utf8 string. At this point there are two paths. If js is on I throw away the string and the tidy tree and run the old system. I have to, because I don't create any of the js nodes corresponding to the tidy tree, so if you want js you still have to use the old system. But if there is no js, I fold the new string into the text buffer, and don't use the old code at all. So I am somewhat forcing you to play along. After all, I need testers, and real world experience. If the new code seg faults or something, (and I'm sure tsp will find the bugs), let me know, and try to run with js so you're using the old code again.
I've run some side by side tests on some very large web pages, and the rendered buffers are almost the same, and when they differ I usually prefer the new format, though that could be a matter of taste. Run jsrt with no js and it works as well as it could. db3 and submit and the post data looks right. Also the line under <noscript> appears. This is really fun, but also tiring, so I may need to take a break for a few days. The next step is to traverse the tidy tree and build the js nodes, a separate call from render() of course, and then we'll be able to use the tidy tree all the time. I know this isn't the end-all design, I understand, but we need to move forward, step by step, and I think we're doing that. Enjoy. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
