What do yall think of the idea of making the js abort on db5 even more violent than it is already? Could we add exit(0) and quit altogether? Or perhaps not on db5, but could I define this on a large unused db level such as db999 or just 1+ the highest that we have currently?
Example: I made a mistake in startwindow which was illegal within js but didn't make compilation fail. I had db5 on. The "js abort due to error while debugging" appears, but it is followed by hundreds more lines of tidy and other output. Might take a little time to understand what happened, and the edbrowse session is shot because javascript is now disabled so there was no point in continuing with non-JS.
thanks Kevin _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
