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 9251 - "When content fails to load (e.g. due to a network error), then the user agent must queue a task to fire a simple event named error at the element instead." is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same applies to <frame>.
Summary: "When content fails to load (e.g. due to a network error), then the user agen...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 21:10 UTC by contributor
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-15 21:10:02 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-iframe-element

Comment:
"When content fails to load (e.g. due to a network error), then the user agent
must queue a task to fire a simple event named error at the element instead."
is pretty vague (e.g. do bad URLs fire onerror? cross-domain failures?) Same
applies to <frame>.

Posted from: 216.239.45.4 by ian@hixie.ch
Comment 1 Ian 'Hixie' Hickson 2010-03-15 21:14:02 UTC 
In practice I expect it should only fire for 4xx and 5xx responses, DNS failures, and network errors. I wouldn't expect it to fire for cross-domain loads of any kind, for URL parsing errors, for JS errors in the page once it has loaded, or for 2xx responses.
Comment 2 Ian 'Hixie' Hickson 2010-03-31 19:39:07 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 diff given below
Rationale: Concurred with reporter's comments.
Comment 3 contributor 2010-03-31 19:41:19 UTC 
Checked in as WHATWG revision r4920.
Check-in comment: Clarify what iframe onerror fires for
http://html5.org/tools/web-apps-tracker?from=4919&to=4920