3 ms·
Voted up for developing Twiddla for IE. I share your sentiment.. I develop against IE first then test it against the "good" browsers... which rarely screw it u
by sam_in_nyc 18y ago
Voted up for developing Twiddla for IE.
I share your sentiment.. I develop against IE first then test it against the "good" browsers... which rarely screw it up. IE sucks for script debugging.. I mean EPIC suck. You're not even told what line of what file is screwed up (IE seems to concatenate everything into 1 file when giving the error report), but I've learned to rely on myself not to make common scripting mistakes, and created a cross-browser "console" object to aid in debugging.
Safari has the worst script debugging on the planet. It essentially tells you whether or not there was an error. Oh, wait... and how many errors, total. Thanks, Safari!
- jasonkester 18y agoGet VS.NET, and suddenly IE has the best script debugging around. Firebug rocks and all, but VS.NET will drop you into a breakpoint will a full call stack, watch, step thru, etc. It's a proper debugger. And yeah, it takes about the same level of effort to develop against IE as it does against FF. The advantage is that your stuff generally then works right in Firefox first try.
- rbritton 18y agoUm, Safari has a full Javascript debugger built in: http://developer.apple.com/internet/safari/faq.html#anchor14 http://developer.apple.com/internet/safari/faq.html#anchor14 (among other google results)
- sam_in_nyc 18y agoAmazing.. I can do console.log(). And if there's an error (which the link provided conveniently has), I get to see the entire file which gave the error. So helpful... I now know which file to sprinkle console.log()s in. Furthermore, it doesn't work at all for dynamically loaded JS. But, then again, there apparently were several Google results.