3 ms·
Only IE (so far) has lied horribly to me in its debugger: http://cl.ly/012t192A2s3Y1A3b3j3H http://cl.ly/012t192A2s3Y1A3b3j3H . How in the world does that happ
by Groxx 15y ago
Only IE (so far) has lied horribly to me in its debugger: http://cl.ly/012t192A2s3Y1A3b3j3H http://cl.ly/012t192A2s3Y1A3b3j3H . How in the world does that happen? For the record, `FireEvent` doesn't exist, but `fireEvent` does.
And then there's the worthless "{...}" object display from the Javascript console...
- altano 15y agoThe horrible "{...}" output for almost everything (and proper callstacks when using named function expressions) are all fixed in IE9. That still puts it dead last for MOST visualizations behind all the other browsers OTHER than IE8, but some things, such as the profiler call tree, are still the best.