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 14174 - onerror: if body can't be parsed then window.onerror should be invoked
Summary: onerror: if body can't be parsed then window.onerror should be invoked
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks: 14175
  Show dependency tree / graph
 
Reported: 2011-09-16 06:50 UTC by contributor
Modified: 2011-11-10 23:32 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-09-16 06:50:05 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html
Multipage: http://www.whatwg.org/C#event-handler-content-attributes
Complete: http://www.whatwg.org/c#event-handler-content-attributes

Comment:
if body can't be parsed then window.onerror should be invoked

Posted from: 85.227.155.223 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.51
Comment 1 Ian 'Hixie' Hickson 2011-10-19 23:49:45 UTC 
Can you elaborate?
Comment 2 Simon Pieters 2011-10-20 21:55:54 UTC 
Step 4

"If body is not parsable as FunctionBody or if parsing detects an early error then abort these steps."

should "report the error" before aborting the steps.
Comment 3 Ian 'Hixie' Hickson 2011-11-03 16:22:57 UTC 
will probably do this as part of bug 14175.
Comment 4 Ian 'Hixie' Hickson 2011-11-10 23:32:08 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see bug 14176
Rationale: Concurred with reporter's comments.