BUILD: Current trunk STEPS TO REPRODUCE: 1) Load attached testcase. 2) Realize there was a JS error. 3) Open web console EXPECTED RESULTS: Web console shows JS error so you can debug ACTUAL RESULTS: Nothing shown. Reloading shows the error from the reload, but reloading is often not an option (think POST result pages, for example; I run into this all the time). This is one of the issues that is forcing me to continue using the old error console.

this will be fixed when bug 587734 lands - or shortly thereafter

(In reply to comment #2) > this will be fixed when bug 587734 lands - or shortly thereafter Actually, I have misspoken. This only fixes messages that are produced by calling window.console.log, info, warn and error. All other messages, (e.g. nsIScriptErrors, etc) will not be cached in case the tab's console is opened. The observers are not started unless a user opens a console. From that moment forward we have listeners in place. Filed bug 601260 to take care of this.

this is assigned to David, but the underlying work is assigned to me. Is there anything to do in this bug other than mark it fixed when bug 601260 is completed?

(In reply to comment #4) > this is assigned to David, but the underlying work is assigned to me. Is there > anything to do in this bug other than mark it fixed when bug 601260 is > completed? You are correct. Lets make this a dupe then.