zlacker

I use the FF devtools daily, and for what I'm working on, it has everything I need to help me get the things I need done. Knowing that I'm not everyone and have plenty to learn, what things are missing from the devtools for you?

>>dylan6+(OP)
The only issue I have (which, is happening less and less lately) is my debugger doesn't jump to the source. It hits and everything pauses, but I don't get routed to it and have to start progressing just to get it to work, which can make the debugger useless as you've gone past what you were looking at. This has happened across machines for years for me, and happens much less in chrome. But doesn't happen enough for me to switch.

>>dylan6+(OP)
I use FF and prefer the devtools.

Chrome's ability to temporarily edit and save changes to JS sources through the debugger editor is fantastic though.

Other than that it's mostly just improvements to what FF already has.

Search could be made much more useful, especially network requests. Searching all request bodies/responses for a particular string/json/regex would be a huge step up.

You can search the response of individual requests but there's a UI bug that makes it look like your filter is no longer applied when you select the next one in the list.

>>Jochim+bL
>Chrome's ability to temporarily edit and save changes to JS sources through the debugger editor is fantastic though.

Does this affect the live code so the change is available immediately? I once had a thought about wondering if this was possible to have the change available without refreshing

>>dylan6+ms1
As far as I know, you have to reload the page sadly.

>>Jochim+NX1
It made no sense for how that could work that I could imagine, but it would be holycrapthatscool if it could. some sort of second JIT or something, but i can only imagine the security nightmare that'd open up