Our javascript debugger, which we enter by jex for javascript execution for historical reasons, but looking at it now I think jdb for javascript debugger would make more sense, what do you think?
Anyways when you enter that mode and make some changes and then leave, edbrowse did not go down the same pathways as say running some onclick code. You could set innerHTML, or add some options to an option list, or createTextNode and appendChild to paste text into the document, and none of that was reflected in the buffer. I have fixed this. As of the latest commit, side effects are processed, and the buffer rerendered, as though you had pushed a button to run onclick js code or some such. This makes it easier to test our dom functions like create and append and innerHTML and the like, and see the results rendered in the buffer. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
