Simplify event terminology. Make 'load' events fired on the Window have the Document as the target. (whatwg r2989)

Simplify event terminology. Make 'load' events fired on the Window have
the Document as the target. (whatwg r2989)

the script block's source
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#the-script-block-s-source
4.11 Interactive elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#interactive-elements
broadcast formchange events
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#broadcast-formchange-events
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#attr-iframe-name
Firing an error event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#fire-an-error-event
checkValidity()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#dom-cva-checkvalidatity
alt
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#attr-img-alt
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#attr-object-name
Firing a show event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#fire-a-show-event
src
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#attr-input-src
statically validate the constraints
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#statically-validate-the-constraints
delays the load event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2153.html#delay-the-load-event

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2152&r2=1.2153&f=h
http://html5.org/tools/web-apps-tracker?from=2988&to=2989

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2152
retrieving revision 1.2153
diff -u -d -r1.2152 -r1.2153
--- Overview.html 26 Apr 2009 06:40:19 -0000 1.2152
+++ Overview.html 26 Apr 2009 19:42:10 -0000 1.2153
@@ -10261,8 +10261,8 @@
 
      <li>
 
-      <p><a href="#fire-a-load-event">Fire a <code title="event-load">load</code>
-      event</a> at the <code><a href="#script">script</a></code> element.</p>
+      <p><a href="#fire-a-simple-event">Fire a simple event</a> called <code title="event-load"><a href="#event-load">load</a></code> at the <code><a href="#script">script</a></code>
+      element.</p>
 
      </li>
 
@@ -14588,12 +14588,13 @@
   <p>The <a href="#concept-task" title="concept-task">task</a> that is <a href="#queue-a-task" title="queue a task">queued</a> by the <a href="#networking-task-source">networking task
   source</a> once the resource has been <a href="#fetch" title="fetch">fetched</a>, must, if the download was successful
   and the image is <i>available</i>, <a href="#queue-a-task">queue a task</a> to
-  <a href="#fire-a-load-event">fire a <code title="event-load">load</code> event</a> on
-  the <code><a href="#the-img-element">img</a></code> element (this happens after <code title="dom-img-complete"><a href="#dom-img-complete">complete</a></code> starts returning true); and
-  otherwise, if the fetching process fails without a response from the
-  remote server, or completes but the image is not a valid or
-  supported image, <a href="#queue-a-task">queue a task</a> to <a href="#fire-an-error-event">fire an <code title="event-error">error</code> event</a> on the
-  <code><a href="#the-img-element">img</a></code> element.</p>
+  <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-load"><a href="#event-load">load</a></code> at the <code><a href="#the-img-element">img</a></code> element (this
+  happens after <code title="dom-img-complete"><a href="#dom-img-complete">complete</a></code> starts
+  returning true); and otherwise, if the fetching process fails
+  without a response from the remote server, or completes but the
+  image is not a valid or supported image, <a href="#queue-a-task">queue a task</a>
+  to <a href="#fire-an-error-event">fire an <code title="event-error">error</code> event</a>
+  on the <code><a href="#the-img-element">img</a></code> element.</p>
 
   <hr><p>What an <code><a href="#the-img-element">img</a></code> element represents depends on the <code title="attr-img-src"><a href="#attr-img-src">src</a></code> attribute and the <code title="attr-img-alt"><a href="#attr-img-alt">alt</a></code> attribute.</p>
 
@@ -15685,9 +15686,10 @@
   name</a> must be set to the empty string.</p>
 
   <p>When content loads in an <code><a href="#the-iframe-element">iframe</a></code>, after any <code title="event-load"><a href="#event-load">load</a></code> events are fired within the content
-  itself, the user agent must <a href="#fire-a-load-event">fire a <code title="event-load">load</code> event</a> at the
-  <code><a href="#the-iframe-element">iframe</a></code> element. When content fails to load (e.g. due to
-  a network error), then the user agent must <a href="#fire-an-error-event">fire an <code title="event-error">error</code> event</a> at the element
+  itself, the user agent must <a href="#fire-a-simple-event">fire a simple event</a> called
+  <code title="event-load"><a href="#event-load">load</a></code> at the <code><a href="#the-iframe-element">iframe</a></code>
+  element. When content fails to load (e.g. due to a network error),
+  then the user agent must <a href="#fire-an-error-event">fire an <code title="event-error">error</code> event</a> at the element
   instead.</p>
 
   <p>When there is an active parser in the <code><a href="#the-iframe-element">iframe</a></code>, and
@@ -16454,9 +16456,10 @@
      <li><p>The element's contents are not part of what the
      <code><a href="#the-object-element">object</a></code> element represents.</p>
 
-     <li><p>Once the resource is completely loaded, <a href="#fire-a-load-event">fire a <code title="event-load">load</code> event</a> at the
-     element.</li> <!-- XXX ordering of events (like with iframe)
-     -->
+     <li><p>Once the resource is completely loaded, <a href="#fire-a-simple-event">fire a
+     simple event</a> called <code title="event-load"><a href="#event-load">load</a></code>
+     at the element.</li> <!-- XXX ordering of events (like with
+     iframe) -->
 
     </ol></li>
 
@@ -27967,7 +27970,7 @@
   <p>The <a href="#concept-task" title="concept-task">task</a> that is <a href="#queue-a-task" title="queue a task">queued</a> by the <a href="#networking-task-source">networking task
   source</a> once the resource has been <a href="#fetch" title="fetch">fetched</a>, must, if the download was successful
   and the image is <i>available</i>, <a href="#queue-a-task">queue a task</a> to
-  <a href="#fire-a-load-event">fire a <code title="event-load">load</code> event</a> on
+  <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-load"><a href="#event-load">load</a></code> at
   the <code><a href="#the-input-element">input</a></code> element; and otherwise, if the fetching
   process fails without a response from the remote server, or
   completes but the image is not a valid or supported image,
@@ -30618,7 +30621,7 @@
     <p>For each element <var title="">field</var> in <var title="">invalid controls</var>, if any, in <a href="#tree-order">tree
     order</a>, run the following substeps:</p>
 
-    <ol><li><p><a href="#fire-a-simple-event">Fire a simple event</a> named <code title="event-invalid">invalid</code> at <var title="">field</var>.</li>
+    <ol><li><p><a href="#fire-a-simple-event">Fire a simple event</a> called <code title="event-invalid">invalid</code> at <var title="">field</var>.</li>
 
      <li><p>If the event was not canceled, then add <var title="">field</var> to <var title="">unhandled invalid
      controls</var>.</li>
@@ -30832,7 +30835,7 @@
   </dl><p>When the <dfn id="dom-cva-checkvalidatity" title="dom-cva-checkValidatity"><code>checkValidity()</code></dfn>
   method is invoked, if the element is a <a href="#candidate-for-constraint-validation">candidate for
   constraint validation</a> and does not <a href="#concept-fv-valid" title="concept-fv-valid">satisfy its constraints</a>, the user
-  agent must <a href="#fire-a-simple-event">fire a simple event</a> named <code title="event-invalid">invalid</code> at the element and return
+  agent must <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-invalid">invalid</code> at the element and return
   false. Otherwise, it must only return true without doing anything
   else.</p>
 
@@ -31616,7 +31619,7 @@
    was to <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a>; let <var title="">event name</var> be <code title="event-formchange">formchange</code>.</li>
 
    <li><p>For each element in <var title="">controls</var>, in
-   <a href="#tree-order">tree order</a>, <a href="#fire-a-simple-event">fire a simple event</a> named
+   <a href="#tree-order">tree order</a>, <a href="#fire-a-simple-event">fire a simple event</a> called
    <var title="">event name</var> at the element.</li>
 
   </ol></div><h3 id="interactive-elements"><span class="secno">4.11 </span>Interactive elements</h3><h4 id="the-details-element"><span class="secno">4.11.1 </span>The <dfn><code>details</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
@@ -37603,14 +37606,7 @@
   to the node on which the menu was fired, and with which the menu was
   associated (which could be an ancestor of the former).</span></p>
 
-  <p><dfn id="fire-a-load-event" title="fire a load event">Firing a <code title="event-load">load</code> event</dfn> means <a href="#fire-a-simple-event" title="fire a
-  simple event">firing a simple event called <code title="event-load">load</code></a>. <!--<dfn title="fire a
-  DOMContentLoaded event">Firing a <code
-  title="event-DOMContentLoaded">DOMContentLoaded</code> event</dfn>
-  means <span title="fire a simple event">firing a simple event called
-  <code
-  title="event-DOMContentLoaded">DOMContentLoaded</code></span>.-->
-  <dfn id="fire-an-error-event" title="fire an error event">Firing an <code title="event-error">error</code> event</dfn> means <a href="#fire-a-simple-event" title="fire
+  <p><dfn id="fire-an-error-event" title="fire an error event">Firing an <code title="event-error">error</code> event</dfn> means <a href="#fire-a-simple-event" title="fire
   a simple event">firing a simple event called <code title="event-error">error</code></a>.</p>
 
   <!-- XXX need to define the dispatching of DOMActivate -->
@@ -52581,10 +52577,12 @@
    readiness</a> to "complete".</li>
 
    <li>If the <code>Document</code> is in a <a href="#browsing-context">browsing
-   context</a>, then <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-load-event" title="fire
-   a load event">fire a <code title="event-load">load</code>
-   event</a> at the <code>Document</code>'s <code><a href="#window">Window</a></code>
-   object.</li>
+   context</a>, then <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a
+   simple event</a> called <code title="event-load"><a href="#event-load">load</a></code> at
+   the <code>Document</code>'s <code><a href="#window">Window</a></code> object, but with
+   its <code title="dom-event-target">target</code> set to the
+   <code>Document</code> object (and the <code title="dom-event-currentTarget">currentTarget</code> set to the
+   <code><a href="#window">Window</a></code> object).</li>
 
    <li>If the <code>Document</code> has a <a href="#pending-state-object">pending state
    object</a>, then <a href="#queue-a-task">queue a task</a> to fire a <code title="event-popstate"><a href="#event-popstate">popstate</a></code> event in no namespace on the

Received on Sunday, 26 April 2009 19:44:23 UTC