Slide 7
Slide 7 text
1. fileName is non standard
2. lineNumber is nonstandard
3. Internet Explorer Sucks
4. Some browser put properties on instances of errors, others on the prototype.
5. The format of the stacktrace is not standard across any browser.
6. Description is only available in IE (but who cares)
7. Number is also there, but who puts error numbers anymore?
8. Chrome uses line, FireFox uses lineNumber, because why wouldn’t they?
9. FireFox has a toSource() method, which sounds cool, but isn’t
10. Old versions of browsers didn’t support errors at all. Because nothing ever goes wrong
11. Using a debugger, not all properties will be visible on error objects, because some browsers don’t treat
them as objects, but as host objects—so they can do whatever they want.
12. Firebug puts its own properties on error objects when debugging, but they aren’t there and things die if you reference
them.
13. So many more, but no one cares at this point.
14. Seriously, debugging this shit will make you very sad.
15. The Internet is broken and nobody cares
JavaScript Error Footnotes