There are many enhancements that would be good to make, but probably not bundled with this one. Go to 3.5.1 first, then other changes can push the third number again. These changes are mostly additions to the DOM, objects that I haven't implemented or even simulated, and as we all saw, when one of these is missing javascript stops in its tracks. That's why edbrowse isn't working on more and more sites. We need to have the same objects and methods, or stubs for these objects and methods, as you might find in a browser. It's just grunt-work, and not very easy or satisfying. A site doesn't work, set db3, track it down, what variable is missing, look it up in a js dom tutorial, what does the variable do, implement it or simulate it. Then move on to the next broken website, and so on. All needs to be done, all good stuff, but rather independent of what we're doing now.
Some of these changes won't happen until the big rewrite, those where js creates brand new thingies that are normally made by html. That's backwards in my path today, so we'll just wait on these. Anyways that's how I see the road ahead. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
