Bug 158192 - ErrorEvent should include the underlying uncaught exception, if any, in the 'error' property
Summary: ErrorEvent should include the underlying uncaught exception, if any, in the '...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks: 158056 55092
  Show dependency tree / graph
 
Reported: 2016-05-29 06:45 PDT by BJ Burg
Modified: 2016-05-29 10:12 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description BJ Burg 2016-05-29 06:45:17 PDT 
From https://www.w3.org/TR/html5/webappapis.html#the-errorevent-interface:

"The error attribute must return the value it was initialized to. When the object is created, this attribute must be initialized to null. Where appropriate, it is set to the object representing the error (e.g. the exception object in the case of an uncaught DOM exception)."
Comment 1 Radar WebKit Bug Importer 2016-05-29 06:45:43 PDT 
<rdar://problem/26534875>