Firefox 30 is out! And excitingly, it now provides column numbers in exception stack traces.
With the column number, we can use source maps to figure out the line of actual code which crashed. This makes debugging much easier in many cases, as you can quickly see what your code was trying to do when it crashed.
IE Firefox Chrome Safari stack property on exceptions 10+ ✔ ✔ ✔ column number in stack trace 10+ 30+ ✔ 7+ error object in window.onerror ✘ 31β+ ✔ ✘ column number in window.onerror 8+ 17+ ✔ 7+
As can be seen Firefox comes a pretty close second to Chrome for exception features. Once Firefox 31 is out (estimated July) with access to the error object from window.onerror (we were involved with fixing that too) there will be nothing to choose between the two.