Get the actual Javascript Error object with [removed]

前端 未结 3 773
有刺的猬
有刺的猬 2020-12-13 08:34

Javascript has this great callback window.onerror. It\'s quite convenient to track any error. However, it calls with the error name, the file name and the line.

相关标签:
3条回答
  • 2020-12-13 09:01

    If you're referring to stack trace of the error object, then AFAIK, this is not possible.

    Simple reason being that a stack trace is related to an execution context in which runtime exceptions (handled with try...catch...finally) were created or thrown (with new Error() or throw).

    Whereas when window.onerror is invoked, it is called within a different context.

    You can get some mileage by inspecting window.event (not available on FF) in your onerror handler.

    0 讨论(0)
  • 2020-12-13 09:14

    this is now possible in some browsers. The spec was updated to include the actual error with stacktrace as the 5th parameter.

    the problem is that not every browser supports this yet, so you could do something like this:

    window.onerror = function(message, filename, lineno, colno, error)
    {
        if(error != null)
        {
            //handle the error with stacktrace in error.stack
        }
        else
        {
            //sadly only 'message', 'filename' and 'lineno' work here
        }
    };
    
    0 讨论(0)
  • 2020-12-13 09:24

    Modern browsers fully support the HTML 5 draft spec for ErrorEvent and window.onerror. In both of these browsers you can either use window.onerror, or (amazingly!) bind to the 'error' event properly:

    // Only Chrome & Opera pass the error object.
    window.onerror = function (message, file, line, col, error) {
        console.log(message, "from", error.stack);
    };
    // Only Chrome & Opera have an error attribute on the event.
    window.addEventListener("error", function (e) {
        console.log(e.error.message, "from", e.error.stack);
    });
    
    0 讨论(0)
提交回复
热议问题