3 ms·
Bad timing for this to happen. Have you guys tried the script debugging in IE8? Wow. IE's script error handling has been so useless for so long that it took
by jasonkester 17y ago
Bad timing for this to happen. Have you guys tried the script debugging in IE8? Wow.
IE's script error handling has been so useless for so long that it took a while to sink in that it's so much better now. As in, it's miles ahead of Firebug. Proper call stack navigation, break-on-error that drops you into the debugger. It just plain works.
For CSS debugging and network traffic inspection, Firebug is still the defacto standard. I don't think it's going anywhere, but it's certainly in second place now when it comes to JS debugging.
- nfriedly 17y agoI agree with you, the new debugger is miles better than the old one, and hasn't crashed on me yet. However, it's still IE. Even with the new debugger, it still tool me nearly 10 hours to figure out that IE was occasionally moving a text range from an iFrame to the parent document when I tried to use the selection.pasteHTML method. I thought it was a bug in my code...