I fear we have reached a point in edbrowse where all the low hanging fruit has been plucked.
I have several sites that "don't work", yet evoke no js errors as they run.
That means all the javascript executes, but doesn't do everything it is suppose to, or does something slightly wrong, or lacks a connection to our nodes in the edbrowse world, or some such.
Some of these sites have 20 js files, some have 50,000 lines of js code.
Most of the js is minimized, and even if you deminimize it, it still has gross one letter variables and no comments, and no way to know what it is suppose to do,
as compared to what it does in edbrowse, and where the paths diverge.

We can only hope to run into some simpler websites that don't work, I call these middle hanging fruit,
and maybe we can find and fix a problem, and that will fix the other site over there, where the fruit is way up high.
Other than that, I don't know what to do.

Another approach is to plow through the 100 acid tests, which is where we started almost a year ago.
The js is clear and readable, although there is a lot of it, and maybe the time has come for that.

Karl Dahlke