[html5] r2992 - [] (0) Clean up event dispatch, with a particular emphasis on whether events get [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sun Apr 26 15:10:43 PDT 2009
Author: ianh
Date: 2009-04-26 15:10:42 -0700 (Sun, 26 Apr 2009)
New Revision: 2992
Modified:
index
source
Log:
[] (0) Clean up event dispatch, with a particular emphasis on whether events get canceled or not.
Modified: index
===================================================================
--- index 2009-04-26 21:05:44 UTC (rev 2991)
+++ index 2009-04-26 22:10:42 UTC (rev 2992)
@@ -8621,11 +8621,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>
@@ -11438,8 +11438,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>
@@ -16767,8 +16767,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>
@@ -18037,8 +18037,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
@@ -18734,8 +18734,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>
@@ -30992,9 +30993,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>
@@ -31128,7 +31130,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
@@ -31491,11 +31494,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>
@@ -34587,7 +34590,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>
@@ -34807,9 +34810,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
@@ -34915,10 +34918,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 -->
@@ -38657,8 +38661,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
@@ -38673,8 +38677,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
@@ -42093,29 +42101,12 @@
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>
+ <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><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 -->
-
<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
that hasn't yet been defined, in the <a href=#refsPROGRESS>[PROGRESS]</a> spec.</p>
@@ -43711,14 +43702,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>
@@ -43730,8 +43726,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
@@ -43749,9 +43745,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>
@@ -43782,16 +43781,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
@@ -43846,7 +43844,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
@@ -43868,8 +43866,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>
@@ -43900,8 +43898,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
@@ -43951,8 +43949,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
@@ -44087,7 +44085,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
@@ -44155,8 +44153,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
@@ -44165,7 +44163,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
@@ -44196,7 +44195,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
@@ -44207,8 +44206,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
@@ -47789,8 +47788,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
@@ -51104,14 +51102,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>
@@ -51212,14 +51210,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>
@@ -51477,7 +51475,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>
@@ -51564,7 +51562,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>
@@ -64148,7 +64146,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
Modified: source
===================================================================
--- source 2009-04-26 21:05:44 UTC (rev 2991)
+++ source 2009-04-26 22:10:42 UTC (rev 2992)
@@ -8956,11 +8956,11 @@
<p>When a user agent is to <dfn>run post-click activation
steps</dfn> on an element, the user agent must <span>fire a simple
event</span> called <code
- title="event-DOMActivate">DOMActivate</code> at that element. The
- default action of this event must be to <span>run final activation
- steps</span> on that element. If the event is canceled, the user
- agent must <span>run canceled activation steps</span> on the element
- instead.</p>
+ title="event-DOMActivate">DOMActivate</code> that is cancelable at
+ that element. The default action of this event must be to <span>run
+ final activation steps</span> on that element. If the event is
+ canceled, the user agent must <span>run canceled activation
+ steps</span> on the element instead.</p>
<p>When a user agent is to <dfn>run pre-click activation steps</dfn>
on an element, it must run the <dfn>pre-click activation steps</dfn>
@@ -12188,9 +12188,8 @@
an HTTP 404 error)</dt>
<dd><p>Executing the script block must just consist of <span
- title="fire an error event">firing an <code
- title="event-error">error</code> event</span> at the
- element.</p></dd>
+ title="fire a simple event">firing a simple event</span> called
+ <code title="event-error">error</code> at the element.</p></dd>
<dt>If the load was successful</dt>
@@ -17997,8 +17996,9 @@
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, <span>queue a task</span>
- to <span>fire an <code title="event-error">error</code> event</span>
- on the <code>img</code> element.</p>
+ to <span>fire a simple event</span> called <code
+ title="event-error">error</code> on the <code>img</code>
+ element.</p>
<hr>
@@ -19353,9 +19353,8 @@
itself, the user agent must <span>fire a simple event</span> called
<code title="event-load">load</code> 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>
+ then the user agent must <span>fire a simple event</span> called
+ <code title="event-error">error</code> 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
@@ -20140,9 +20139,9 @@
<li><p>If the load failed (e.g. the <span>URL</span> could not be
<span title="resolve a url">resolved</span>, there was an HTTP
- 404 error, there was a DNS error), <span>fire an <code
- title="event-error">error</code> event</span> at the element,
- then jump to the last step in the overall set of steps
+ 404 error, there was a DNS error), <span>fire a simple
+ event</span> called <code title="event-error">error</code> at the
+ element, then jump to the last step in the overall set of steps
(fallback).</p></li>
<li><p>Determine the <var title="">resource type</var>, as follows:</p>
@@ -34560,9 +34559,11 @@
back to the values they had before the <span>pre-click activation
steps</span> were run. The <span>activation behavior</span> is to
<span>fire a simple event</span> called <code
- title="event-change">change</code> at the element, then
- <span>broadcast <code title="event-formchange">formchange</code>
- events</span> at the element's <span>form owner</span>.</p>
+ title="event-change">change</code> at the element<!-- It's not
+ cancelable. Once this fires, the control is checked, end of
+ story. -->, then <span>broadcast <code
+ title="event-formchange">formchange</code> events</span> at the
+ element's <span>form owner</span>.</p>
<p><strong>Constraint validation:</strong> If the element is <i
title="concept-input-required">required</i> and its <span
@@ -34721,7 +34722,8 @@
the element's <span title="concept-fe-checked">checkedness</span> to
false. The <span>activation behavior</span> is to <span>fire a
simple event</span> called <code title="event-change">change</code>
- at the element, then <span>broadcast <code
+ at the element<!-- It's not cancelable. Once this fires, the control
+ is checked, end of story. -->, then <span>broadcast <code
title="event-formchange">formchange</code> events</span> at the
element's <span>form owner</span>.</p>
@@ -35133,12 +35135,12 @@
source</span> once the resource has been <span
title="fetch">fetched</span>, must, if the download was successful
and the image is <i>available</i>, <span>queue a task</span> to
- <span>fire a simple event</span> called <code title="event-load">load</code> at
- the <code>input</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,
- <span>queue a task</span> to <span>fire an <code
- title="event-error">error</code> event</span> on the
+ <span>fire a simple event</span> called <code
+ title="event-load">load</code> at the <code>input</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, <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-error">error</code> on the
<code>input</code> element.</p>
<hr>
@@ -38895,7 +38897,7 @@
<ol>
<li><p><span>Fire a simple event</span> called <code
- title="event-invalid">invalid</code> at <var
+ title="event-invalid">invalid</code> that is cancelable at <var
title="">field</var>.</p></li>
<li><p>If the event was not canceled, then add <var
@@ -39142,9 +39144,9 @@
constraint validation</span> and does not <span
title="concept-fv-valid">satisfy its constraints</span>, the user
agent must <span>fire a simple event</span> called <code
- title="event-invalid">invalid</code> at the element and return
- false. Otherwise, it must only return true without doing anything
- else.</p>
+ 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
title="dom-cva-validationMessage"><code>validationMessage</code></dfn>
@@ -39260,11 +39262,11 @@
<li><p>If the <var title="">submitter</var> is anything but a
<code>form</code> element, then <span>fire a simple event</span>
- 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).</p></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).</p></li>
<!-- if you add any steps between the "lock" and "unlock" lines,
make sure to update the step immediately before the "lock" line -->
@@ -43583,8 +43585,9 @@
<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 <span>fire a <code title="">contextmenu</code> event</span> on
- the element for which the menu was requested.</p>
+ must <span>fire a simple event</span> 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
@@ -43603,8 +43606,13 @@
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 <span>fire a <code title="">show</code>
- event</span> on the relevant <code>menu</code> element.</p>
+ the user agent must <span>fire a simple event</span> called <code
+ title="event-show">show</code> at the <code>menu</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 <span title="building menus and tool
@@ -47625,36 +47633,13 @@
values appropriately describing the state of the key input device at
the time the event is created.</p>
- <p><dfn 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 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>
+ 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><dfn title="fire a show event">Firing a <code
- title="event-show">show</code> event</dfn> means <span title="fire a
- simple event">firing a simple event called <code
- title="event-show">show</code></span>. <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 title="fire an error event">Firing an <code
- title="event-error">error</code> event</dfn> means <span title="fire
- a simple event">firing a simple event called <code
- title="event-error">error</code></span>.</p>
-
- <!-- XXX need to define the dispatching of DOMActivate -->
-
<p class="XXX"><dfn title="fire a progress event">Firing a
progress event called <var title="">e</var></dfn> means something
that hasn't yet been defined, in the <a
@@ -49490,16 +49475,21 @@
a simple event</span> called <code
title="event-checking">checking</code> at the
<code>ApplicationCache</code> singleton of that <span>cache
- host</span>.</p></li>
+ host</span>. 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.</p></li>
<li><p>If these steps were invoked with a <span>cache
host</span>, and the <span
title="concept-appcache-status">status</span> of <var
title="">cache group</var> is <i>downloading</i>, then also
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-downloading">downloading</code> at the
- <code>ApplicationCache</code> singleton of that <span>cache
- host</span>.</p></li>
+ called <code title="event-downloading">downloading</code> that is
+ cancelable at the <code>ApplicationCache</code> singleton of that
+ <span>cache host</span>. 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.</p></li>
<li><p>If the <span title="concept-appcache-status">status</span>
of the <var title="">cache group</var> is either <i>checking</i>
@@ -49513,8 +49503,9 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-checking">checking</code>
- at the <code>ApplicationCache</code> singleton of the <span>cache
+ event</span> that is cancelable called <code
+ title="event-checking">checking</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
host</span>. 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
@@ -49535,9 +49526,12 @@
<li><p>If this is a <span title="concept-appcache-cache">cache
attempt</span>, then this algorithm was invoked with a <span>cache
host</span>; <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-checking">checking</code> at
- the <code>ApplicationCache</code> singleton of that <span>cache
- host</span>.</p></li>
+ event</span> called <code title="event-checking">checking</code>
+ that is cancelable at the <code>ApplicationCache</code> singleton
+ of that <span>cache host</span>. 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.</p></li>
<li>
@@ -49577,17 +49571,18 @@
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
event</span> called <code title="event-obsolete">obsolete</code>
- at the <code>ApplicationCache</code> singleton of the <span>cache
- host</span>. 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.</p></li>
+ that is cancelable at the <code>ApplicationCache</code> singleton
+ of the <span>cache host</span>. 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.</p></li>
<li><p>For each entry in <var title="">cache group</var>'s <span
title="concept-appcache-pending-masters">list of pending master
entries</span>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-error">error</code> (not
- <code title="event-obsolete">obsolete</code>!) at the
+ event</span> that is cancelable called <code
+ title="event-error">error</code> (not <code
+ title="event-obsolete">obsolete</code>!) at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span> the <code>Document</code> for this entry, if there
still is one. The default action of this event should be the
@@ -49654,7 +49649,7 @@
<p>If the download failed (e.g. the connection times out, or the
user cancels the download), then <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> that is cancelable called <code
title="event-error">error</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span> the <code>Document</code> for this entry, if there
@@ -49679,8 +49674,9 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-noupdate">noupdate</code>
- at the <code>ApplicationCache</code> singleton of the <span>cache
+ event</span> that is cancelable called <code
+ title="event-noupdate">noupdate</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
host</span>. 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.</p></li>
@@ -49718,8 +49714,9 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache group</var>,
- <span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-downloading">downloading</code> at the
+ <span>queue a task</span> to <span>fire a simple event</span> that
+ is cancelable called <code
+ title="event-downloading">downloading</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user that
@@ -49776,8 +49773,9 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-progress">progress</code>
- at the <code>ApplicationCache</code> singleton of the <span>cache
+ event</span> that is cancelable called <code
+ title="event-progress">progress</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
host</span>. 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
@@ -49929,7 +49927,8 @@
<var title="">new cache</var>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code title="event-error">error</code> at the
+ event</span> that is cancelable called <code
+ title="event-error">error</code> at the
<code>ApplicationCache</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
@@ -50010,8 +50009,9 @@
attempt</span>, then for each <span>cache host</span> associated
with an <span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-cached">cached</code> at
- the <code>ApplicationCache</code> singleton of the <span>cache
+ event</span> that is cancelable called <code
+ title="event-cached">cached</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
host</span>. 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
@@ -50021,8 +50021,8 @@
title="concept-appcache-upgrade">upgrade attempt</span>. For each
<span>cache host</span> associated with an <span>application
cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-updateready">updateready</code> at the
+ task</span> to <span>fire a simple event</span> that is cancelable
+ called <code title="event-updateready">updateready</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user that
@@ -50060,7 +50060,8 @@
its <span>application cache</span>, if it has one.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code title="event-error">error</code> at the
+ event</span> that is cancelable called <code
+ title="event-error">error</code> at the
<code>ApplicationCache</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
@@ -50073,8 +50074,8 @@
<li><p>For each <span>cache host</span> still associated with an
<span>application cache</span> in <var title="">cache group</var>,
- <span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-error">error</code> at the
+ <span>queue a task</span> to <span>fire a simple event</span> that
+ is cancelable called <code title="event-error">error</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user that
@@ -52664,7 +52665,7 @@
<p>When this happens, the user agent must dispatch an event with the
name <code>storage</code>, with no namespace, which does not bubble
- but is cancelable, and which uses the <code>StorageEvent</code>
+ and is not cancelable, and which uses the <code>StorageEvent</code>
interface, at each <code>Window</code> object whose
<code>Document</code> object both has a <code>Storage</code> object
that is affected, and is <span>fully active</span>.</p>
@@ -55801,8 +55802,8 @@
</li>
- <li><p><span>Fire a simple event</span> that doesn't bubble called
- <code title="event-focus">focus</code> at the element.</p></li>
+ <li><p><span>Fire a simple event</span> called <code
+ title="event-focus">focus</code> at the element.</p></li>
</ol>
@@ -60318,9 +60319,9 @@
<p>Whenever a runtime script error occurs in one of the worker's
scripts, if the error did not occur while handling a previous script
- error, the user agent must <span>queue a task</span> to <span>fire
- an error event</span> at the <code>WorkerGlobalScope</code>
- object.</p>
+ error, the user agent must <span>queue a task</span> to <span>fire a
+ simple event</span> called <code title="event-error">error</code> at
+ the <code>WorkerGlobalScope</code> object.</p>
<p>For shared workers, if the error is still <i title="">not
handled</i> afterwards, or if the error occured while handling a
@@ -60329,12 +60330,12 @@
<p>For dedicated workers, if the error is still <i title="">not
handled</i> afterwards, or if the error occured while handling a
previous script error, the user agent must further <span>queue a
- task</span> to <span>fire an error event</span> at the
+ task</span> to <span>fire a worker error event</span> at the
<code>Worker</code> object associated with the worker.</p>
- <p>When the user agent is to <dfn>fire an error event</dfn> at a
- <code>Worker</code> object, it must dispatch an event that uses the
- <code>ErrorEvent</code> interface, with the name <code
+ <p>When the user agent is to <dfn>fire a worker error event</dfn> at
+ a <code>Worker</code> object, it must dispatch an event that uses
+ the <code>ErrorEvent</code> interface, with the name <code
title="event-error">error</code>, that doesn't bubble and is
cancelable, with its <code
title="dom-ErrorEvent-message">message</code>, <code
@@ -60343,10 +60344,10 @@
appropriately. The default action of this event depends on whether
the <code>Worker</code> object is itself in a worker. If it is, and
that worker is also a dedicated worker, then the user agent must
- again <span>queue a task</span> to <span>fire an error event</span>
- at the <code>Worker</code> object associated with <em>that</em>
- worker. Otherwise, then the error should be reported to the
- user.</p>
+ again <span>queue a task</span> to <span>fire a worker error
+ event</span> at the <code>Worker</code> object associated with
+ <em>that</em> worker. Otherwise, then the error should be reported
+ to the user.</p>
<hr>
@@ -60613,13 +60614,13 @@
<li><p>Create an event that uses the <code>MessageEvent</code>
interface, with the name <code
title="event-connect">connect</code>, which does not bubble, is
- cancelable, has no default action, has a <code
+ not cancelable, has no default action, has a <code
title="dom-MessageEvent-data">data</code> attribute whose value
is the empty string and has a <code
- title="dom-MessageEvent-ports">ports</code>
- attribute whose value is an array containing only the newly
- created port, and <span>queue a task</span> to dispatch the
- event at <var title="">worker global scope</var>.</p></li>
+ title="dom-MessageEvent-ports">ports</code> attribute whose
+ value is an array containing only the newly created port, and
+ <span>queue a task</span> to dispatch the event at <var
+ title="">worker global scope</var>.</p></li>
<li><p>Abort all these steps.</p></li>
@@ -60655,14 +60656,14 @@
<li><p>Create an event that uses the <code>MessageEvent</code>
interface, with the name <code
- title="event-connect">connect</code>, which does not bubble, is
+ title="event-connect">connect</code>, which does not bubble, is not
cancelable, has no default action, has a <code
title="dom-MessageEvent-data">data</code> attribute whose value is
the empty string and has a <code
- title="dom-MessageEvent-ports">ports</code> attribute
- whose value is an array containing only the newly created port, and
- <span>queue a task</span> to dispatch the event at <var
- title="">worker global scope</var>.</p></li>
+ title="dom-MessageEvent-ports">ports</code> attribute whose value
+ is an array containing only the newly created port, and <span>queue
+ a task</span> to dispatch the event at <var title="">worker global
+ scope</var>.</p></li>
<li>
@@ -61503,7 +61504,7 @@
<li><p>Otherwise, create an event that uses the
<code>MessageEvent</code> interface, with the event 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. The <code
title="dom-MessageEvent-data">data</code> attribute must be set to
the value of the <var title="">data</var> buffer, the <code
@@ -61897,7 +61898,7 @@
<p>When <i>a Web Socket message has been received</i> with text <var
title="">data</var>, the user agent must create an event that uses
the <code>MessageEvent</code> interface, with the event name <code
- title="event-message">message</code>, which does not bubble, is
+ title="event-message">message</code>, which does not bubble, is not
cancelable, has no default action, and whose <code
title="dom-MessageEvent-data">data</code> attribute is set to <var
title="">data</var>, and <span>queue a task</span> to dispatch it at
@@ -63021,7 +63022,7 @@
<p>Create an event that uses the <code>MessageEvent</code>
interface, with the event name <code
title="event-message">message</code>, which does not bubble, is
- cancelable, and has no default action. The <code
+ not cancelable, and has no default action. The <code
title="dom-MessageEvent-data">data</code> attribute must be set to
the value of <var title="">message clone</var>, the <code
title="dom-MessageEvent-origin">origin</code> attribute must be
@@ -63029,9 +63030,9 @@
origin">Unicode serialization</span> of the <span>origin</span> of
the script that invoked the method, and the <code
title="dom-MessageEvent-source">source</code> attribute must be
- set to the <span>script's global object</span>.</p> <!-- invariant:
- the global scope is always a Window if the script can see this
- method -->
+ set to the <span>script's global object</span>.</p> <!--
+ invariant: the global scope is always a Window if the script can
+ see this method -->
</li>
@@ -63150,7 +63151,7 @@
<p>Create an event that uses the <code>MessageEvent</code>
interface, with the event name <code
title="event-message">message</code>, which does not bubble, is
- cancelable, and has no default action. The <code
+ not cancelable, and has no default action. The <code
title="dom-MessageEvent-data">data</code> attribute must be set to
the value of <var title="">message clone</var>, the <code
title="dom-MessageEvent-origin">origin</code> attribute must be
@@ -63158,9 +63159,9 @@
origin">Unicode serialization</span> of the <span>origin</span> of
the script that invoked the method, and the <code
title="dom-MessageEvent-source">source</code> attribute must be
- set to the <span>script's global object</span>.</p> <!-- invariant:
- the global scope is always a Window if the script can see this
- method -->
+ set to the <span>script's global object</span>.</p> <!--
+ invariant: the global scope is always a Window if the script can
+ see this method -->
</li>
@@ -63465,7 +63466,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>
@@ -63563,7 +63564,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>
@@ -75227,7 +75228,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
More information about the Commit-Watchers
mailing list