After bug 1243550 -jsconsole command line argument the new Browser console does not show up on startup in Win XP (it does on Linux). Also there are some errors from webtools: 11:47:06.332 ReferenceError: reference to undefined property Cc['@mozilla.org/dom /slow-script-debug;1'] devtools-browser.js:438:9 11:47:06.335 TypeError: Cc['@mozilla.org/dom/slow-script-debug;1'] is undefined devtools-browser.js:438
I cab reproduce it on windows10
Please fix this.
Does this work on Firefox?
I can't reproduce this on mac and don't have a windows development environment set up. While this is unfortuante, using a key combination on startup to open the js console is a viable workaround.
This is Windows-only. As it's a startup issue, bug 1321955 may help, though I doubt it as this was filed 6 months ago.
(In reply to aleth [:aleth] from comment #6) > As it's a startup issue, bug 1321955 may help Now I've done it, I don't think it will help. Maybe jorgk can take a look when he has time as he is on Windows...
Sorry, I have very limited time. You could save me time if you told me what you want me to do. Start TB on the command line with -jsconsole and look for what exactly?
(In reply to Jorg K (GMT+1) from comment #8) > Sorry, I have very limited time. You could save me time if you told me what > you want me to do. Start TB on the command line with -jsconsole and look for > what exactly? It seems clear from comment 0 and comment 1 the error console does not pop up on Windows. It needs debugging by someone on Windows ;) It's probably not the most important bug though.