- Though file name is available in the
.stackproperty, only Firefox and Safari provide this as an explicit property, and that too with different property names (FF:
- All browsers string-format the stack subtly differently. There's no standard regarding stack formatting. Firefox has the least informative stack property. I'm going to cut Firefox some slack though, since they were the first to expose this property. That said, this might change in the future. Worth keeping an eye on this discussion.
- Firefox doesn't provide column numbers in the stack at all. However, it does provide a
.columnNumberproperty which is only useful for the first stack frame.
.numberproperty (IE) is practically useless. It points to IE's internal representation of errors.
.lineNumber(Firefox) properties give the line number of the first stack frame of the error. No one else provides a similar property, though this data is available in the
.stackeverywhere except Firefox.
.toString()formatting seems consistent, and similar to the formatting of the error message in
window.onerror. That is, it uses the format
name + ": " + message. The only exception to this, of course, is that
window.onerrorformats errors differently when the source file has x-domain restrictions.
- Column numbers in the
.stackproperty are only available in IE10+ and Chrome. Opera provides a
.stacktraceproperty in addition to
.stackthat has column numbers (go figure!). No other browser provides column numbers in the stack trace. As mentioned above, Firefox does provide an explicit
.columnNumberproperty that's only useful for the first stack frame.
- No stack support for IE<10. Nothing. Zilch.