I have been reviewing the status of WebKit and their implementation of window.onerror. They implemented it recently after several years in the queue. The unfortunate thing about their implementation is that it does not give access to any way of getting the full error stack. Both IE and Mozilla have had capabilities to get the call stack (albeit not standard or similar).
The issue with WebKit is that they are following the WhatWG specification exactly for 184.108.40.206 Runtime script errors. This specification does not give any reference to access the error object or stack information.
My question is, what is the possibility of having the specification for 220.127.116.11 Runtime script errors updated to include a fourth parameter for the error object which was thrown.
Having the error object at the error handler is first common sense from a cross language perspective and it gives access to the object that "should" contain access to the stack and finally gives access to the error class, error message, throw stack access (errPrevious = error.getCause();).
I would be glad to make a detailed business case for this change but I have no idea on what the next steps would be to get this done.
Thanks for your time,
- Timothy (Jsd) Quinn