4 ms·
For me the biggest problem is that it doesn't clear upon reload. Having to keep track of which messages/errors came from the previous page is really annoying.
by Skalman 14y ago
For me the biggest problem is that it doesn't clear upon reload. Having to keep track of which messages/errors came from the previous page is really annoying.
Edit: Also, viewing objects is inferior compared to Chrome's tools.
- AndrewDucker 14y agoI'd go with that. I can't think of any reason why I'd want to see the information from a previous load - I just want to see what's going on right now, clearly.
- nathanstitt 14y agoI can because I just found that very useful. Think of code that has an error in an window.onbeforeunload handler. By the time the console displays the error the page has switched. Without being able to view the errors from the previous page, this would have been impossible to catch.
- mihai_sucan 14y agoWe just changed the way you can inspect objects in the Web Console, check out a Firefox Nightly. For more details you can read: http://www.robodesign.ro/mihai/blog/web-console-improvements-and-the-new-browser-console http://www.robodesign.ro/mihai/blog/web-console-improvements... Also, we have an open bug about clearing the web console after page reload. See: https://bugzilla.mozilla.org/show_bug.cgi?id=705921 https://bugzilla.mozilla.org/show_bug.cgi?id=705921
- Skalman 14y agoOkay, nice. Did you also remove the need for clicking those tiny arrows to expand?
- mihai_sucan 14y agoYes.
- Ygg2 14y agoYou might want the ability to clear console on page reload as an option. It seems useful and people should be able to enable/disable it (or was it added to new nightly).
- FuzzyDunlop 14y agoI also think that clicking on the link to an error should go to the debugger panel, rather than opening the source in another popup.
- past 14y agoThis is already implemented in Firefox 22.