This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15893 - Whenever an uncaught runtime script error occurs in one of the scripts associated with a Document, the user agent must report the error at the URL of the resource containing the script (as established when the script was created), with the problematic pos
Summary: Whenever an uncaught runtime script error occurs in one of the scripts associ...
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-04 19:12 UTC by contributor
Modified: 2012-07-18 18:40 UTC (History)
2 users (show)

See Also:


Attachments

Description contributor 2012-02-04 19:12:53 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#processing-model-1
Multipage: http://www.whatwg.org/C#event-loops
Complete: http://www.whatwg.org/c#event-loops

Comment:
Whenever an uncaught runtime script error occurs in one of the scripts
associated with a Document, the user agent must report the error at the URL of
the resource containing the script (as established when the script was
created), with the problematic position (line number and column number) in
that resource, in the script's origin, using the onerror event handler of the
script's global object. If the error is still not handled after this, then the
error may be reported to the user.

Posted from: 139.195.46.13
User agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)