8837 2010-01-29 12:37:58 +0000 Initial about:blank should fire DOMFrameContentLoaded and load events when not navigated immediately 2010-10-04 14:31:12 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED P2 normal --- 1 hsivonen ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31336 0 hsivonen 2010-01-29 12:37:58 +0000 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. 31954 1 ian 2010-02-14 04:50:20 +0000 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. 32331 2 contributor 2010-02-18 02:27:27 +0000 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 32332 3 contributor 2010-02-18 02:41:49 +0000 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 32333 4 ian 2010-02-18 03:01:57 +0000 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.