3 ms·

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 s

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
  > Also, make sure you try the new net monitor in Firefox Nightlies. I do, and I love it. It's an excellent start. Let me make it clear, I love what you guys are doing. It's wonderful.

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
> Also, make sure you try the new net monitor in Firefox Nightlies. I do, and I love it. It's an excellent start. Let me make it clear, I love what you guys are doing. It's wonderful.