On 2/4/13, Nathan Broadbent nathan@gmail.com wrote:
Hi,
Hi Nathan -
The current information passed to window.onerror rarely provides
sufficient information to find the cause of the error. The column
That's putting it mildly.
number argument will be a big step forward, but a stack trace
On Feb 4, 2013, at 2:40 PM, Garrett Smith dhtmlkitc...@gmail.com wrote:
That's fair enough. Though not all exceptions are Errors -- DOMException
currently isn't, though I think some people want it to somehow inherit
from
Error.
Why not?
That's something lost in the mists of time, however
On Mon, Feb 4, 2013 at 5:44 PM, Oliver Hunt oli...@apple.com wrote:
...
That's tricky - what is your stack trace? You can very easily end up
leaking private information across frames.
window.onerror is triggered across non-same origin frames?
- E
