9 ms·

What's wrong with it? Honest question? I've used both a bit but I see no big discrepancies?

by Ygg2 14y ago

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 ago
  I'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 ago
    I 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 ago
  We 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 ago
    Okay, nice. Did you also remove the need for clicking those tiny arrows to expand?
    - mihai_sucan 14y ago
      Yes.
  - Ygg2 14y ago
    You 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 ago
  I 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 ago
    This is already implemented in Firefox 22.
ConceitedCode 14y ago
At first it felt significantly worse for me, but as I started using it there is no significant difference. Webkit's is prettier and I like the being able to refresh to clear it though.
jasonlotito 14y ago
Breakpoints are limited - In chrome, I can watch for events and have it break on them. If I'm wanting to debug minified code, in chrome I make it readable and set breakpoints. Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger. From the tools, no way to see data like cookies or local storage (Cookies can be seen on the network tab, but it's not the same). Chrome has this in a Resources tab. Chrome's timeline. The style editing options in the inspector are limited. Sure, the style editor is a colorized text editor, but there is no easy way to edit styles as in Chrome. Chrome, I can set states and work with them without worry. Editing CSS is also easier with auto-complete. Basically, editing in CSS in Chrome is better than in Firefox. There are a lot of little things. They are catching up. I can get some of these things in Firebug, but then I'd be using Firebug. Finally, the console is limited. In Chrome, I can bring up the console on any section. This is important, as it lets me use the console while looking at the information I'm currently working with for reference. There are things I like, and I'm looking forward to the day it's comparable and meets my needs.
- Offler 14y ago
  "Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger." This is huge for me, it makes debugging impossible when loading.
- mihai_sucan 14y ago
  Each of the aspects you tackle are known and we are working towards improvements in each area. Even myself as a web developer I find things that we are missing - I understand your pains here! Break on events and break on XHR is something we really want to have ASAP. I expect these will be among the first ones to land - from the things you mention. Also, make sure you try the new net monitor in Firefox Nightlies.
  - jasonlotito 14y ago
richardwhiuk 14y ago
In Chrome, you can choose to pause on uncaught exceptions, as opposed to all exceptions or none, which is the case in Ffx

What's wrong with it? Honest question? I've used both a bit but I see no big discrepancies?

by Ygg2 14y ago

What's wrong with it? Honest question? I've used both a bit but I see no big discrepancies?

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 ago
I'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 ago
  I 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 ago
We 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 ago
  Okay, nice. Did you also remove the need for clicking those tiny arrows to expand?
  - mihai_sucan 14y ago
    Yes.
- Ygg2 14y ago
  You 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 ago
I 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 ago
  This is already implemented in Firefox 22.

ConceitedCode 14y ago

At first it felt significantly worse for me, but as I started using it there is no significant difference. Webkit's is prettier and I like the being able to refresh to clear it though.

jasonlotito 14y ago

Breakpoints are limited - In chrome, I can watch for events and have it break on them. If I'm wanting to debug minified code, in chrome I make it readable and set breakpoints. Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger. From the tools, no way to see data like cookies or local storage (Cookies can be seen on the network tab, but it's not the same). Chrome has this in a Resources tab. Chrome's timeline. The style editing options in the inspector are limited. Sure, the style editor is a colorized text editor, but there is no easy way to edit styles as in Chrome. Chrome, I can set states and work with them without worry. Editing CSS is also easier with auto-complete. Basically, editing in CSS in Chrome is better than in Firefox. There are a lot of little things. They are catching up. I can get some of these things in Firebug, but then I'd be using Firebug. Finally, the console is limited. In Chrome, I can bring up the console on any section. This is important, as it lets me use the console while looking at the information I'm currently working with for reference. There are things I like, and I'm looking forward to the day it's comparable and meets my needs.

Offler 14y ago
"Would be nice to edit the JavaScript as well in the process of debugging it. JS Breakpoints currently (in nightly) block loading of the JavaScript file the breakpoint is in. The file is loaded, just not visible in the debugger." This is huge for me, it makes debugging impossible when loading.
mihai_sucan 14y ago
Each of the aspects you tackle are known and we are working towards improvements in each area. Even myself as a web developer I find things that we are missing - I understand your pains here! Break on events and break on XHR is something we really want to have ASAP. I expect these will be among the first ones to land - from the things you mention. Also, make sure you try the new net monitor in Firefox Nightlies.
- jasonlotito 14y ago

richardwhiuk 14y ago

In Chrome, you can choose to pause on uncaught exceptions, as opposed to all exceptions or none, which is the case in Ffx