User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150326004005 Steps to reproduce: When an error is thrown, for example by visiting: https://vast-plains-7555.herokuapp.com/items I open the console to inspect Actual results: The console nicely displays the error, and the source of the error, but the stack trace is no-where to be found. Expected results: I would expect the stack-trace to be visible (or at least easily accessible), as this would allow for a much more actionable bug squash. Additionally, each line of the stack should likely be clickable and when clicked should open that line in the debugger. This will enable a developer to quickly drop the needed break-points to explore the issue further.

Note that `console.log(someErrorObject)` shows the stack (although it isn't click-able: bug 1151138), but random code that throws an error and doesn't catch it, resulting in a message sent to the console, does not show the stack. Additionally, I think we should have the stack collapsible (and collapsed by default) like `console.exception("foo")` results in.