JavaScript error messages are no longer dumped to the application console in optimised builds (Win32). This is a problem. Mike McCabe has talked to me about development of a XUL based JavaScript console but I was not aware that the activation of this console would result in the loss of simple reporting to the app console, which is a vital toolin application development esp at this stage of the project when the app is often crash happy, and the only place that can be relied on to hold error and other information is the native app console, which will usually show the point of program failure. I am aware that console dumping is available in debug builds, however since all my work is XUL and JS, I seldom need to build, and since optimised builds are quickly available and much faster on my portable than debug, it is simply more convenient for me to develop using them. If appconsole dumping is not considered appropriate by default, then a pref should be set up to allow this, maybe javascript.error.mirror_to_stderr or something similar. Setting severity to blocker, cc'ing don as this is a serious impediment to my beta2 feature work.

Fixed - I've made errors go to the system console regardless.

Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

vrfy fixed 2000062408 win98 -- JS errors go to the console