4 ms·

I keep an old copy of Firefox around just so I can have Firebug 2. Here's what I'd like DevTools to do: * Make a breakpoints view, not one embedded into a mas

I keep an old copy of Firefox around just so I can have Firebug 2. Here's what I'd like DevTools to do: * Make a breakpoints view, not one embedded into a massive list of unsorted (or sorted-by-load-date I guess?!) files that changes over time. If that can't be done (or is against the design philosophy of DevTools), letting me choose the sort order would be nice (e.g. recently-viewed files first, or files with breakpoints, etc ..... and uh, remembering those files and/or settings through refreshes would be fantastic... I miss it from Firebug 2). It's nice because after/during refreshes the breakpoint view lets you pull up the file the second it's loaded, instead of scrolling around in the file list until you find it. * Make it a LOT more obvious when DevTools is stopped at a breakpoint. * DevTools doesn't handle initial focus the way Firebug does. As in, when you pull up Firebug via the selection icon--oh, DevTools needs that selection icon for the toolbar--it goes straight to the dom node you selected. * Make DevTools stop crashing. It stops working. Constantly. The console will just stop printing output, and the DOM view just stops displaying HTML, requiring a browser restart. (When this happens, if you, say, pull up the console and type "1" and hit enter, usually the console echos "1" back to you. When you're in this state, it's not echoed back, though, oddly, some script messages still pop in.) * Make "debugger" start working again. There are some places where--for who knows what reason--both Firebug and DevTools have ignored breakpoints I've put in, and I've been able to get around it in Firebug by explicitly putting in "debugger;" into my code. You definitely know you're in deep kimchi when you need "debugger;". * Make DevTools remember the state of my "Log Response/Request Bodies" checkbox. It gets reset constantly, and it should be remembered across refreshes. Heck, even by URL. If I turn it on, leave it on. Also, for one of my websites, it can't load the source. It just shows "eval" as the filenames over and over with nothing in them. Firebug 2 loads it just fine. Long live Firebug 2!

gear54rus 11y ago
> There are some places where--for who knows what reason--both Firebug and DevTools have ignored breakpoints I've put in... This might be because the js file you put them in is loaded with another URL and is therefore considered a different file (and therefore does not have your breakpoint). This is what I've experienced before. This is a bs design, of course, and files should probably be compared via means other than URL.
- inanutshellus 11y ago
  Sure, I get it, but when it happens you're just in a bad world and you can either try to put breakpoints in every copy of the file that Firebug/Devtools detects, or you can say *&$% it, and add "debugger;" in the file.
inanutshellus 11y ago
Oh, and DevTools doesn't honor my breakpoints. They "slide" down to the next line DevTools thinks it can actually stop on. For one thing, the number of times it "slides" past valid code is shocking. Right now I'm looking at a perfectly boring JS file and the breakpoints are only stopping on the function declaration lines. The contents of the functions are being slid past. Once I restart my browser they'll work again. For another, as a time-saver I put breakpoints on lines that /will/ be valid when I refresh (saves me from having to refresh the file twice), so it simply doing as I told it to do would be grand.

gear54rus 11y ago

> There are some places where--for who knows what reason--both Firebug and DevTools have ignored breakpoints I've put in... This might be because the js file you put them in is loaded with another URL and is therefore considered a different file (and therefore does not have your breakpoint). This is what I've experienced before. This is a bs design, of course, and files should probably be compared via means other than URL.

inanutshellus 11y ago
Sure, I get it, but when it happens you're just in a bad world and you can either try to put breakpoints in every copy of the file that Firebug/Devtools detects, or you can say *&$% it, and add "debugger;" in the file.

inanutshellus 11y ago

Oh, and DevTools doesn't honor my breakpoints. They "slide" down to the next line DevTools thinks it can actually stop on. For one thing, the number of times it "slides" past valid code is shocking. Right now I'm looking at a perfectly boring JS file and the breakpoints are only stopping on the function declaration lines. The contents of the functions are being slid past. Once I restart my browser they'll work again. For another, as a time-saver I put breakpoints on lines that /will/ be valid when I refresh (saves me from having to refresh the file twice), so it simply doing as I told it to do would be grand.