W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2009

html5/spec Overview.html,1.2155,1.2156

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 26 Apr 2009 22:10:50 +0000
To: public-html-commits@w3.org
Message-Id: <E1LyCYk-0001xG-90@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv7500

Modified Files:
	Overview.html 
Log Message:
Clean up event dispatch, with a particular emphasis on whether events get canceled or not. (whatwg r2992)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2155
retrieving revision 1.2156
diff -u -d -r1.2155 -r1.2156
--- Overview.html	26 Apr 2009 21:05:50 -0000	1.2155
+++ Overview.html	26 Apr 2009 22:10:47 -0000	1.2156
@@ -7703,11 +7703,11 @@
 
   <p>When a user agent is to <dfn id="run-post-click-activation-steps">run post-click activation
   steps</dfn> on an element, the user agent must <a href="#fire-a-simple-event">fire a simple
-  event</a> called <code title="event-DOMActivate">DOMActivate</code> at that element. The
-  default action of this event must be to <a href="#run-final-activation-steps">run final activation
-  steps</a> on that element. If the event is canceled, the user
-  agent must <a href="#run-canceled-activation-steps">run canceled activation steps</a> on the element
-  instead.</p>
+  event</a> called <code title="event-DOMActivate">DOMActivate</code> that is cancelable at
+  that element. The default action of this event must be to <a href="#run-final-activation-steps">run
+  final activation steps</a> on that element. If the event is
+  canceled, the user agent must <a href="#run-canceled-activation-steps">run canceled activation
+  steps</a> on the element instead.</p>
 
   <p>When a user agent is to <dfn id="run-pre-click-activation-steps">run pre-click activation steps</dfn>
   on an element, it must run the <dfn id="pre-click-activation-steps">pre-click activation steps</dfn>
@@ -10167,8 +10167,8 @@
   <dl class="switch"><dt>If the load resulted in an error (for example a DNS error, or
    an HTTP 404 error)</dt>
 
-   <dd><p>Executing the script block must just consist of <a href="#fire-an-error-event" title="fire an error event">firing an <code title="event-error">error</code> event</a> at the
-   element.</dd>
+   <dd><p>Executing the script block must just consist of <a href="#fire-a-simple-event" title="fire a simple event">firing a simple event</a> called
+   <code title="event-error"><a href="#event-error">error</a></code> at the element.</dd>
 
    <dt>If the load was successful</dt>
 
@@ -14593,8 +14593,8 @@
   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>
+  to <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-error"><a href="#event-error">error</a></code> 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>
 
@@ -15689,8 +15689,8 @@
   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>
+  then the user agent must <a href="#fire-a-simple-event">fire a simple event</a> called
+  <code title="event-error"><a href="#event-error">error</a></code> at the element instead.</p>
 
   <p>When there is an active parser in the <code><a href="#the-iframe-element">iframe</a></code>, and
   when anything in the <code><a href="#the-iframe-element">iframe</a></code> that is <a href="#delay-the-load-event" title="delay
@@ -16317,8 +16317,9 @@
 
      <li><p>If the load failed (e.g. the <a href="#url">URL</a> could not be
      <a href="#resolve-a-url" title="resolve a url">resolved</a>, there was an HTTP
-     404 error, there was a DNS error), <a href="#fire-an-error-event">fire an <code title="event-error">error</code> event</a> at the element,
-     then jump to the last step in the overall set of steps
+     404 error, there was a DNS error), <a href="#fire-a-simple-event">fire a simple
+     event</a> called <code title="event-error"><a href="#event-error">error</a></code> at the
+     element, then jump to the last step in the overall set of steps
      (fallback).</li>
 
      <li><p>Determine the <var title="">resource type</var>, as follows:</p>
@@ -27541,9 +27542,10 @@
   the element's <code title="dom-input-indeterminate"><a href="#dom-input-indeterminate">indeterminate</a></code> DOM attribute
   back to the values they had before the <a href="#pre-click-activation-steps">pre-click activation
   steps</a> were run. The <a href="#activation-behavior">activation behavior</a> is to
-  <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-change">change</code> at the element, then
-  <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code>
-  events</a> at the element's <a href="#form-owner">form owner</a>.</p>
+  <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-change">change</code> at the element<!-- It's not
+  cancelable. Once this fires, the control is checked, end of
+  story. -->, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
+  element's <a href="#form-owner">form owner</a>.</p>
 
   <p><strong>Constraint validation:</strong> If the element is <i title="concept-input-required"><a href="#concept-input-required">required</a></i> and its <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> is false, then the
   element is <a href="#suffering-from-being-missing">suffering from being missing</a>.</p>
@@ -27661,7 +27663,8 @@
   the element's <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> to
   false. The <a href="#activation-behavior">activation behavior</a> is to <a href="#fire-a-simple-event">fire a
   simple event</a> called <code title="event-change">change</code>
-  at the element, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
+  at the element<!-- It's not cancelable. Once this fires, the control
+  is checked, end of story. -->, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
   element's <a href="#form-owner">form owner</a>.</p>
 
   <p><strong>Constraint validation:</strong> If the element is <i title="concept-input-required"><a href="#concept-input-required">required</a></i> and all of the
@@ -27975,11 +27978,11 @@
   <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-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,
-  <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
+  <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, <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-error"><a href="#event-error">error</a></code> on the
   <code><a href="#the-input-element">input</a></code> element.</p>
 
   <hr></div><p>The <dfn id="attr-input-alt" title="attr-input-alt"><code>alt</code></dfn> attribute
@@ -30626,7 +30629,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> called <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> that is cancelable 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>
@@ -30840,9 +30843,9 @@
   </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> called <code title="event-invalid">invalid</code> at the element and return
-  false. Otherwise, it must only return true without doing anything
-  else.</p>
+  agent must <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-invalid">invalid</code> that is cancelable (but has no
+  default action) at the element and return false. Otherwise, it must
+  only return true without doing anything else.</p>
 
   <p>The <dfn id="dom-cva-validationmessage" title="dom-cva-validationMessage"><code>validationMessage</code></dfn>
   attribute must return the empty string if the element is not a
@@ -30929,10 +30932,11 @@
 
    <li><p>If the <var title="">submitter</var> is anything but a
    <code><a href="#the-form-element">form</a></code> element, then <a href="#fire-a-simple-event">fire a simple event</a>
-   that bubbles<!--XXX check it bubbles-->, named <code title="event-submit">submit</code>, at <var title="">form</var>. If
-   the event's default action is prevented (i.e. if the event is
-   canceled) then abort these steps. Otherwise, continue (effectively
-   the default action is to perform the submission).</li>
+   that is cancelable called <code title="event-submit">submit</code>,
+   at <var title="">form</var>. If the event's default action is
+   prevented (i.e. if the event is canceled) then abort these
+   steps. Otherwise, continue (effectively the default action is to
+   perform the submission).</li>
 
    <!-- if you add any steps between the "lock" and "unlock" lines,
    make sure to update the step immediately before the "lock" line -->
@@ -34435,8 +34439,8 @@
 
   <p>When an element's context menu is requested (e.g. by the user
   right-clicking the element, or pressing a context menu key), the UA
-  must <a href="#fire-a-contextmenu-event">fire a <code title="">contextmenu</code> event</a> on
-  the element for which the menu was requested.</p>
+  must <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-contextmenu">contextmenu</code> that bubbles and is
+  cancelable at the element for which the menu was requested.</p>
 
   <p class="note">Typically, therefore, the firing of the <code title="event-contextmenu">contextmenu</code> event will be the
   default action of a <code title="mouseup">mouseup</code> or <code title="event-keyup">keyup</code> event. The exact sequence of events
@@ -34451,8 +34455,12 @@
   span in a paragraph with a context menu should show the menu).</p>
 
   <p>If the element <em>does</em> have a context menu assigned, then
-  the user agent must <a href="#fire-a-show-event">fire a <code title="">show</code>
-  event</a> on the relevant <code><a href="#menus">menu</a></code> element.</p>
+  the user agent must <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-show">show</code> at the <code><a href="#menus">menu</a></code>
+  element. <span class="XXX">Actually this should fire an event that
+  has modifier information (shift/ctrl etc), as well as having a
+  pointer 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>The default action of <em>this</em> event is that the user agent
   must show a context menu <a href="#building-menus-and-tool-bars" title="building menus and tool
@@ -37593,28 +37601,11 @@
   values appropriately describing the state of the key input device at
   the time the event is created.</p>
 
-  <p><dfn id="fire-a-contextmenu-event" title="fire a contextmenu event">Firing a <code title="event-contextmenu">contextmenu</code> event</dfn> means that
-  a <code title="event-contextmenu">contextmenu</code> event with no
-  namespace, which bubbles and is cancelable, and which uses the
-  <code>Event</code> interface, must be dispatched at the given
-  target.</p>
-
   <p><dfn id="fire-a-simple-event" title="fire a simple event">Firing a simple event called
-  <var title="">e</var></dfn> means that an event with the name <var title="">e</var>, with no namespace, which does not bubble but is
-  cancelable (unless otherwise stated), and which uses the
-  <code>Event</code> interface, must be dispatched at the given
-  target.</p>
-
-  <p><dfn id="fire-a-show-event" title="fire a show event">Firing a <code title="event-show">show</code> event</dfn> means <a href="#fire-a-simple-event" title="fire a
-  simple event">firing a simple event called <code title="event-show">show</code></a>. <span class="XXX">Actually this should fire an event that has
-  modifier information (shift/ctrl etc), as well as having a pointer
-  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-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 -->
+  <var title="">e</var></dfn> means that an event with the name <var title="">e</var>, with no namespace, which does not bubble (unless
+  otherwise stated) and is not cancelable (unless otherwise stated),
+  and which uses the <code>Event</code> interface, must be dispatched
+  at the given target.</p>
 
   <p class="XXX"><dfn id="fire-a-progress-event" title="fire a progress event">Firing a
   progress event called <var title="">e</var></dfn> means something
@@ -39083,14 +39074,19 @@
      <i>downloading</i>, 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-checking">checking</code> at the
      <code><a href="#applicationcache">ApplicationCache</a></code> singleton of that <a href="#cache-host">cache
-     host</a>.</li>
+     host</a>. The default action of this event should be the
+     display of some sort of user interface indicating to the user
+     that the user agent is checking to see if it can download the
+     application.</li>
 
      <li><p>If these steps were invoked with a <a href="#cache-host">cache
      host</a>, and the <a href="#concept-appcache-status" title="concept-appcache-status">status</a> of <var title="">cache group</var> is <i>downloading</i>, then also
      <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-downloading">downloading</code> at the
-     <code><a href="#applicationcache">ApplicationCache</a></code> singleton of that <a href="#cache-host">cache
-     host</a>.</li>
+     called <code title="event-downloading">downloading</code> that is
+     cancelable at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of that
+     <a href="#cache-host">cache host</a>. The default action of this event should
+     be the display of some sort of user interface indicating to the
+     user the application is being downloaded.</li>
 
      <li><p>If the <a href="#concept-appcache-status" title="concept-appcache-status">status</a>
      of the <var title="">cache group</var> is either <i>checking</i>
@@ -39102,8 +39098,8 @@
      <li><p>For each <a href="#cache-host">cache host</a> associated with an
      <a href="#application-cache">application cache</a> in <var title="">cache
      group</var>, <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-checking">checking</code>
-     at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
+     event</a> that is cancelable called <code title="event-checking">checking</code> at the
+     <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
      host</a>. The default action of these events should be the
      display of some sort of user interface indicating to the user
      that the user agent is checking for the availability of
@@ -39121,9 +39117,12 @@
    <li><p>If this is a <a href="#concept-appcache-cache" title="concept-appcache-cache">cache
    attempt</a>, then this algorithm was invoked with a <a href="#cache-host">cache
    host</a>; <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-checking">checking</code> at
-   the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of that <a href="#cache-host">cache
-   host</a>.</li>
+   event</a> called <code title="event-checking">checking</code>
+   that is cancelable at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton
+   of that <a href="#cache-host">cache host</a>. The default action of this event
+   should be the display of some sort of user interface indicating to
+   the user that the user agent is checking for the availability of
+   updates.</li>
 
    <li>
 
@@ -39154,16 +39153,15 @@
      <a href="#application-cache">application cache</a> in <var title="">cache
      group</var>, <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-obsolete">obsolete</code>
-     at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
-     host</a>. The default action of these events should be the
-     display of some sort of user interface indicating to the user
-     that the application is no longer available for offline
-     use.</li>
+     that is cancelable at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton
+     of the <a href="#cache-host">cache host</a>. The default action of these
+     events should be the display of some sort of user interface
+     indicating to the user that the application is no longer
+     available for offline use.</li>
 
      <li><p>For each entry in <var title="">cache group</var>'s <a href="#concept-appcache-pending-masters" title="concept-appcache-pending-masters">list of pending master
      entries</a>, <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-error"><a href="#event-error">error</a></code> (not
-     <code title="event-obsolete">obsolete</code>!) at the
+     event</a> that is cancelable called <code title="event-error"><a href="#event-error">error</a></code> (not <code title="event-obsolete">obsolete</code>!) at the
      <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
      host</a> the <code>Document</code> for this entry, if there
      still is one. The default action of this event should be the
@@ -39218,7 +39216,7 @@
 
       <p>If the download failed (e.g. the connection times out, or the
       user cancels the download), 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-error"><a href="#event-error">error</a></code> at the
+      <a href="#fire-a-simple-event">fire a simple event</a> that is cancelable called <code title="event-error"><a href="#event-error">error</a></code> at the
       <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
       host</a> the <code>Document</code> for this entry, if there
       still is one. The default action of this event should be the
@@ -39240,8 +39238,8 @@
      <li><p>For each <a href="#cache-host">cache host</a> associated with an
      <a href="#application-cache">application cache</a> in <var title="">cache
      group</var>, <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-noupdate">noupdate</code>
-     at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
+     event</a> that is cancelable called <code title="event-noupdate">noupdate</code> at the
+     <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
      host</a>. The default action of these events should be the
      display of some sort of user interface indicating to the user
      that the application is up to date.</li>
@@ -39272,8 +39270,8 @@
 
    <li><p>For each <a href="#cache-host">cache host</a> associated with an
    <a href="#application-cache">application cache</a> in <var title="">cache group</var>,
-   <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-downloading">downloading</code> at the
+   <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that
+   is cancelable called <code title="event-downloading">downloading</code> at the
    <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
    host</a>. The default action of these events should be the
    display of some sort of user interface indicating to the user that
@@ -39323,8 +39321,8 @@
      <li><p>For each <a href="#cache-host">cache host</a> associated with an
      <a href="#application-cache">application cache</a> in <var title="">cache
      group</var>, <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-progress"><a href="#event-progress">progress</a></code>
-     at the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
+     event</a> that is cancelable called <code title="event-progress"><a href="#event-progress">progress</a></code> at the
+     <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
      host</a>. The default action of these events should be the
      display of some sort of user interface indicating to the user
      that a file is being downloaded in preparation for updating the
@@ -39459,7 +39457,7 @@
      <var title="">new cache</var>.</li>
 
      <li><p><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-error"><a href="#event-error">error</a></code> at the
+     event</a> that is cancelable called <code title="event-error"><a href="#event-error">error</a></code> at the
      <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the
      <code>Document</code> for this entry, if there still is one. The
      default action of this event should be the display of some sort
@@ -39527,8 +39525,8 @@
     attempt</a>, then for each <a href="#cache-host">cache host</a> associated
     with an <a href="#application-cache">application cache</a> in <var title="">cache
     group</var>, <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-cached">cached</code> at
-    the <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
+    event</a> that is cancelable called <code title="event-cached">cached</code> at the
+    <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
     host</a>. The default action of these events should be the
     display of some sort of user interface indicating to the user that
     the application has been cached and that they can now use it
@@ -39537,7 +39535,8 @@
     <p>Otherwise, it is an <a href="#concept-appcache-upgrade" title="concept-appcache-upgrade">upgrade attempt</a>. For each
     <a href="#cache-host">cache host</a> associated with an <a href="#application-cache">application
     cache</a> in <var title="">cache group</var>, <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-updateready">updateready</code> at the
+    task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that is cancelable
+    called <code title="event-updateready">updateready</code> at the
     <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
     host</a>. The default action of these events should be the
     display of some sort of user interface indicating to the user that
@@ -39568,7 +39567,7 @@
      its <a href="#application-cache">application cache</a>, if it has one.</li>
 
      <li><p><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-error"><a href="#event-error">error</a></code> at the
+     event</a> that is cancelable called <code title="event-error"><a href="#event-error">error</a></code> at the
      <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the
      <code>Document</code> for this entry, if there still is one. The
      default action of these events should be the display of some sort
@@ -39579,8 +39578,8 @@
 
    <li><p>For each <a href="#cache-host">cache host</a> still associated with an
    <a href="#application-cache">application cache</a> in <var title="">cache group</var>,
-   <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-error"><a href="#event-error">error</a></code> at the
+   <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that
+   is cancelable called <code title="event-error"><a href="#event-error">error</a></code> at the
    <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
    host</a>. The default action of these events should be the
    display of some sort of user interface indicating to the user that
@@ -42643,8 +42642,7 @@
 
    </li>
 
-   <li><p><a href="#fire-a-simple-event">Fire a simple event</a> that doesn't bubble called
-   <code title="event-focus">focus</code> at the element.</li>
+   <li><p><a href="#fire-a-simple-event">Fire a simple event</a> called <code title="event-focus">focus</code> at the element.</li>
 
   </ol><p>User agents must run the <a href="#focusing-steps">focusing steps</a> for an
   element whenever the user moves the focus to a
@@ -45671,14 +45669,14 @@
 
     <p>Create an event that uses the <code><a href="#messageevent">MessageEvent</a></code>
     interface, with the event name <code title="event-message"><a href="#event-message">message</a></code>, which does not bubble, is
-    cancelable, and has no default action. The <code title="dom-MessageEvent-data"><a href="#dom-messageevent-data">data</a></code> attribute must be set to
+    not cancelable, and has no default action. The <code title="dom-MessageEvent-data"><a href="#dom-messageevent-data">data</a></code> attribute must be set to
     the value of <var title="">message clone</var>, the <code title="dom-MessageEvent-origin"><a href="#dom-messageevent-origin">origin</a></code> attribute must be
     set to the <a href="#unicode-serialization-of-an-origin" title="Unicode serialization of an
     origin">Unicode serialization</a> of the <a href="#origin-0">origin</a> of
     the script that invoked the method, and the <code title="dom-MessageEvent-source"><a href="#dom-messageevent-source">source</a></code> attribute must be
-    set to the <a href="#script-s-global-object">script's global object</a>.</p> <!-- invariant:
-    the global scope is always a Window if the script can see this
-    method -->
+    set to the <a href="#script-s-global-object">script's global object</a>.</p> <!--
+    invariant: the global scope is always a Window if the script can
+    see this method -->
 
    </li>
 
@@ -45776,14 +45774,14 @@
 
     <p>Create an event that uses the <code><a href="#messageevent">MessageEvent</a></code>
     interface, with the event name <code title="event-message"><a href="#event-message">message</a></code>, which does not bubble, is
-    cancelable, and has no default action. The <code title="dom-MessageEvent-data"><a href="#dom-messageevent-data">data</a></code> attribute must be set to
+    not cancelable, and has no default action. The <code title="dom-MessageEvent-data"><a href="#dom-messageevent-data">data</a></code> attribute must be set to
     the value of <var title="">message clone</var>, the <code title="dom-MessageEvent-origin"><a href="#dom-messageevent-origin">origin</a></code> attribute must be
     set to the <a href="#unicode-serialization-of-an-origin" title="Unicode serialization of an
     origin">Unicode serialization</a> of the <a href="#origin-0">origin</a> of
     the script that invoked the method, and the <code title="dom-MessageEvent-source"><a href="#dom-messageevent-source">source</a></code> attribute must be
-    set to the <a href="#script-s-global-object">script's global object</a>.</p> <!-- invariant:
-    the global scope is always a Window if the script can see this
-    method -->
+    set to the <a href="#script-s-global-object">script's global object</a>.</p> <!--
+    invariant: the global scope is always a Window if the script can
+    see this method -->
 
    </li>
 
@@ -46013,7 +46011,7 @@
    <var title="">source port</var> is entangled.</li>
 
    <li><p>Create an event that uses the <code><a href="#messageevent">MessageEvent</a></code>
-   interface, with the name <code title="event-message"><a href="#event-message">message</a></code>, which does not bubble, is
+   interface, with the name <code title="event-message"><a href="#event-message">message</a></code>, which does not bubble, is not
    cancelable, and has no default action.</li>
 
    <li><p>Let the <code title="dom-MessageEvent-data"><a href="#dom-messageevent-data">data</a></code>
@@ -46100,7 +46098,7 @@
 
    <li><p>Create an event that uses the <code>MessageEvent</code>
    interface, with the name <code
-   title="event-message">message</code>, which does not bubble, is
+   title="event-message">message</code>, which does not bubble, is not
    cancelable, and has no default action.</p></li>
 
    <li><p>Let the <code title="dom-MessageEvent-data">data</code>
@@ -58322,7 +58320,7 @@
        back/forward
  XXX * need to become consistent about whether or not to quote keyword
        ("<code title="">foo</code>" vs <code>foo</code>)
- XXX * need to properly xref events throughout, mark up DOMActivate, etc
+ XXX * need to properly xref events throughout
  XXX * onclick="" only fires if it is a MouseEvent ?
  XXX * hsivonen makes the following suggestions:
        > To make document conformance a more useful concept for the purpose of catching
Received on Sunday, 26 April 2009 22:11:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 26 April 2009 22:11:04 GMT