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 8837 - Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately
Summary: Initial about:blank should fire DOMFrameContentLoaded and load events when no...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-29 12:37 UTC by Henri Sivonen
Modified: 2010-10-04 14:31 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-01-29 12:37:58 UTC 
When the creation of a browsing context doesn't start a navigation to another URL, the DOMFrameContentLoaded and load events should fire (asynchronously) for the initial about:blank document.

Failing to fire these events broke enough test cases and deviates from current browser practice so that I didn't bother to gather evidence about breaking the Web, but it seems reasonable to expect the failure to fire these events to break the Web.
Comment 1 Ian 'Hixie' Hickson 2010-02-14 04:50:20 UTC 
Ok so this only seems to actually affect <iframe>, <iframe src="{unresolvable}">, <iframe src="about:blank">, and <object data="about:blank">. <frame> and window.open() are already handled since they actually load about:blank properly, with no magic. I can handle this pretty easily by just adding a few cases to the <iframe> and <object> algorithms.
Comment 2 contributor 2010-02-18 02:27:27 UTC 
Checked in as WHATWG revision r4772.
Check-in comment: Make blank <iframe>s fire 'load' events when created.
http://html5.org/tools/web-apps-tracker?from=4771&to=4772
Comment 3 contributor 2010-02-18 02:41:49 UTC 
Checked in as WHATWG revision r4773.
Check-in comment: Make blank <object>s with browsing contexts fire 'load' events when the browing context is created.
http://html5.org/tools/web-apps-tracker?from=4772&to=4773
Comment 4 Ian 'Hixie' Hickson 2010-02-18 03:01:57 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 diffs given above
Rationale: Concurred with reporter's comments.