[html5] r832 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-05-21 18:59:07 -0700 (Mon, 21 May 2007)
New Revision: 832

Modified:
   index
   source
Log:
[] (0) Define 'load' event processing for <iframe> elements ( http://www.hixie.ch/tests/adhoc/html/frames/iframes/007.html )

Modified: index
===================================================================
--- index	2007-05-19 08:45:23 UTC (rev 831)
+++ index	2007-05-22 01:59:07 UTC (rev 832)
@@ -22,7 +22,7 @@
 
    <h1 id=html-5>HTML 5</h1>
 
-   <h2 class="no-num no-toc" id=working>Working Draft — 19 May 2007</h2>
+   <h2 class="no-num no-toc" id=working>Working Draft — 22 May 2007</h2>
 
    <p>You can take part in this work. <a
     href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -12062,19 +12062,30 @@
    attribute is not set when the element is created, the browsing context
    will remain at the initial <code>about:blank</code> page.
 
-  <p>The download of the resource must <a href="#delays">delay the <code
+  <p>When content loads in an <code><a href="#iframe">iframe</a></code>,
+   after any <code title=event-load><a href="#load0">load</a></code> events
+   are fired within the content itself, the user agent must <a
+   href="#firing4">fire a <code title=event-load>load</code> event</a> at the
+   <code><a href="#iframe">iframe</a></code> element. When content fails to
+   load (e.g. due to a network error), then the user agent must <a
+   href="#firing5">fire an <code title=event-error>error</code> event</a> at
+   the element instead.
+
+  <p>When there is an active parser in the <code><a
+   href="#iframe">iframe</a></code>, and when anything in the <code><a
+   href="#iframe">iframe</a></code> that is <a href="#delays" title="delay
+   the load event">delaying the <code title=event-load>load</code> event</a>
+   in the <code><a href="#iframe">iframe</a></code>'s <a
+   href="#browsing0">browsing context</a>, the <code><a
+   href="#iframe">iframe</a></code> must <a href="#delays">delay the <code
    title=event-load>load</code> event</a>.
 
-  <p>When content loads in an <code><a href="#iframe">iframe</a></code>, the
-   user agent must <a href="#firing4">fire a <code
-   title=event-load>load</code> event</a> at the <code><a
-   href="#iframe">iframe</a></code> element. When content fails to load (e.g.
-   due to a network error), then the user agent must <a href="#firing5">fire
-   an <code title=event-error>error</code> event</a> at the element instead.
+  <p class=note>If, during the handling of the <code title=event-load><a
+   href="#load0">load</a></code> event, the <a href="#browsing0">browsing
+   context</a> in the <code><a href="#iframe">iframe</a></code> is again <a
+   href="#navigate" title=navigate>navigated</a>, that will further <a
+   href="#delays">delay the <code title=event-load>load</code> event</a>.
 
-  <p class=big-issue>order of events when content is also firing its own
-   load/error?
-
   <p>An <code><a href="#iframe">iframe</a></code> element never has <a
    href="#fallback">fallback content</a>, as it will always create a nested
    <a href="#browsing0">browsing context</a>, regardless of whether the

Modified: source
===================================================================
--- source	2007-05-19 08:45:23 UTC (rev 831)
+++ source	2007-05-22 01:59:07 UTC (rev 832)
@@ -10091,19 +10091,28 @@
   set when the element is created, the browsing context will remain at
   the initial <code>about:blank</code> page.</p>
 
-  <p>The download of the resource must <span>delay the <code
+  <p>When content loads in an <code>iframe</code>, after any <code
+  title="event-load">load</code> events are fired within the content
+  itself, the user agent must <span>fire a <code
+  title="event-load">load</code> event</span> at the
+  <code>iframe</code> element. When content fails to load (e.g. due to
+  a network error), then the user agent must <span>fire an <code
+  title="event-error">error</code> event</span> at the element
+  instead.</p>
+
+  <p>When there is an active parser in the <code>iframe</code>, and
+  when anything in the <code>iframe</code> that is <span title="delay
+  the load event">delaying the <code title="event-load">load</code>
+  event</span> in the <code>iframe</code>'s <span>browsing
+  context</span>, the <code>iframe</code> must <span>delay the <code
   title="event-load">load</code> event</span>.</p>
 
-  <p>When content loads in an <code>iframe</code>, the user agent must
-  <span>fire a <code title="event-load">load</code> event</span> at
-  the <code>iframe</code> element. When content fails to load
-  (e.g. due to a network error), then the user agent must <span>fire
-  an <code title="event-error">error</code> event</span> at the
-  element instead.</p>
+  <p class="note">If, during the handling of the <code
+  title="event-load">load</code> event, the <span>browsing
+  context</span> in the <code>iframe</code> is again <span
+  title="navigate">navigated</span>, that will further <span>delay the
+  <code title="event-load">load</code> event</span>.</p>
 
-  <p class="big-issue">order of events when content is also firing its
-  own load/error?</p>
-
   <p>An <code>iframe</code> element never has <span>fallback
   content</span>, as it will always create a nested <span>browsing
   context</span>, regardless of whether the specified initial contents