- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 29 Sep 2009 00:31:59 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20709
Modified Files:
Overview.html
Log Message:
Rename 'event handler attributes' to 'event handlers' to reduce confusion with the actual attributes. (whatwg r4013)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3174
retrieving revision 1.3175
diff -u -d -r1.3174 -r1.3175
--- Overview.html 29 Sep 2009 00:13:48 -0000 1.3174
+++ Overview.html 29 Sep 2009 00:31:56 -0000 1.3175
@@ -840,8 +840,8 @@
<li><a href="#javascript-protocol"><span class="secno">6.5.5 </span>The <code title="">javascript:</code> protocol</a></li>
<li><a href="#events"><span class="secno">6.5.6 </span>Events</a>
<ol>
- <li><a href="#event-handler-attributes"><span class="secno">6.5.6.1 </span>Event handler attributes</a></li>
- <li><a href="#event-handler-attributes-on-elements-document-objects-and-window-objects"><span class="secno">6.5.6.2 </span>Event handler attributes on elements, <code>Document</code> objects, and <code>Window</code> objects</a></li>
+ <li><a href="#event-handler-attributes"><span class="secno">6.5.6.1 </span>event handlers</a></li>
+ <li><a href="#event-handlers-on-elements-document-objects-and-window-objects"><span class="secno">6.5.6.2 </span>Event handlers on elements, <code>Document</code> objects, and <code>Window</code> objects</a></li>
<li><a href="#event-firing"><span class="secno">6.5.6.3 </span>Event firing</a></li>
<li><a href="#events-and-the-window-object"><span class="secno">6.5.6.4 </span>Events and the <code>Window</code> object</a></li>
<li><a href="#runtime-script-errors"><span class="secno">6.5.6.5 </span>Runtime script errors</a></ol></ol></li>
@@ -6966,7 +6966,7 @@
<li><code title="handler-onwaiting"><a href="#handler-onwaiting">onwaiting</a></code></li>
</ul><p class="note">The attributes marked with an asterisk have a
different meaning when specified on <code><a href="#the-body-element-0">body</a></code> elements as
- those elements expose <a href="#event-handler-attributes-0">event handler attributes</a> of the
+ those elements expose <a href="#event-handlers">event handlers</a> of the
<code><a href="#window">Window</a></code> object with the same names.<hr><p><a href="#custom-data-attribute" title="custom data attribute">Custom data attributes</a>
(e.g. <code title="">data-foldername</code> or <code title="">data-msgid</code>) can be specified on any <a href="#html-elements" title="HTML elements">HTML element</a>, to store custom data
specific to the page.<hr><p>In <a href="#html-documents">HTML documents</a>, elements in the <a href="#html-namespace-0">HTML
@@ -11453,13 +11453,13 @@
<code><a href="#the-body-element-0">body</a></code> element.</p>
</div><p>The <code><a href="#the-body-element-0">body</a></code> element exposes as <a href="#event-handler-content-attributes">event handler
- content attributes</a> a number of the <a href="#event-handler-attributes-0">event handler
- attributes</a> of the <code><a href="#window">Window</a></code> object. It also mirrors
- their <a href="#event-handler-idl-attributes">event handler IDL attributes</a>.<p>The <code title="handler-window-onblur"><a href="#handler-window-onblur">onblur</a></code>, <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code>, <code title="handler-window-onfocus"><a href="#handler-window-onfocus">onfocus</a></code>, and <code title="handler-window-onload"><a href="#handler-window-onload">onload</a></code> <a href="#event-handler-attributes-0">event handler
- attributes</a> of the <code><a href="#window">Window</a></code> object, exposed on the
- <code><a href="#the-body-element-0">body</a></code> element, shadow the generic <a href="#event-handler-attributes-0">event handler
- attributes</a> with the same names normally supported by
- <a href="#html-elements">HTML elements</a>.<p class="example">Thus, for example, a bubbling <code title="event-error">error</code> event fired on a child of <a href="#the-body-element">the
+ content attributes</a> a number of the <a href="#event-handlers">event
+ handlers</a> of the <code><a href="#window">Window</a></code> object. It also mirrors
+ their <a href="#event-handler-idl-attributes">event handler IDL attributes</a>.<p>The <code title="handler-window-onblur"><a href="#handler-window-onblur">onblur</a></code>, <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code>, <code title="handler-window-onfocus"><a href="#handler-window-onfocus">onfocus</a></code>, and <code title="handler-window-onload"><a href="#handler-window-onload">onload</a></code> <a href="#event-handlers">event
+ handlers</a> of the <code><a href="#window">Window</a></code> object, exposed on the
+ <code><a href="#the-body-element-0">body</a></code> element, shadow the generic <a href="#event-handlers">event
+ handlers</a> with the same names normally supported by <a href="#html-elements">HTML
+ elements</a>.<p class="example">Thus, for example, a bubbling <code title="event-error">error</code> event fired on a child of <a href="#the-body-element">the
body element</a> of a <code>Document</code> would first trigger
the <code title="handler-onerror"><a href="#handler-onerror">onerror</a></code> <a href="#event-handler-content-attributes">event handler
content attributes</a> of that element, then that of the root
@@ -11468,10 +11468,10 @@
attribute</a> on the <code><a href="#the-body-element-0">body</a></code> element. This is because
the event would bubble from the target, to the <code><a href="#the-body-element-0">body</a></code>, to
the <code><a href="#the-html-element-0">html</a></code>, to the <code>Document</code>, to the
- <code><a href="#window">Window</a></code>, and the <a href="#event-handler-attributes-0" title="event handler
- attributes">event handler attribute</a> on the <code><a href="#the-body-element-0">body</a></code>
- is watching the <code><a href="#window">Window</a></code> not the <code><a href="#the-body-element-0">body</a></code>. A
- regular event listener attached to the <code><a href="#the-body-element-0">body</a></code> using <code title="">addEventListener()</code>, however, would fire when the
+ <code><a href="#window">Window</a></code>, and the <a href="#event-handlers" title="event handlers">event
+ handler</a> on the <code><a href="#the-body-element-0">body</a></code> is watching the
+ <code><a href="#window">Window</a></code> not the <code><a href="#the-body-element-0">body</a></code>. A regular event
+ listener attached to the <code><a href="#the-body-element-0">body</a></code> using <code title="">addEventListener()</code>, however, would fire when the
event bubbled through the <code><a href="#the-body-element-0">body</a></code> and not when it reaches
the <code><a href="#window">Window</a></code> object.<div class="example">
@@ -17392,10 +17392,9 @@
<p class="warning">If the <code title="attr-iframe-sandbox"><a href="#attr-iframe-sandbox">sandbox</a></code> attribute is
dynamically added after the <code><a href="#the-iframe-element">iframe</a></code> has loaded a page,
scripts already compiled by that page (whether in
- <code><a href="#script">script</a></code> elements, or in <a href="#event-handler-attributes-0">event handler
- attributes</a>, or elsewhere) will continue to run. Only
- <em>new</em> scripts will be prevented from executing by this
- flag.</p>
+ <code><a href="#script">script</a></code> elements, or in <a href="#event-handlers">event handlers</a>,
+ or elsewhere) will continue to run. Only <em>new</em> scripts will
+ be prevented from executing by this flag.</p>
</dd>
@@ -45224,30 +45223,28 @@
</div><h4 id="events"><span class="secno">6.5.6 </span>Events</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><div class="impl">
- <h5 id="event-handler-attributes"><span class="secno">6.5.6.1 </span>Event handler attributes</h5>
+ <h5 id="event-handler-attributes"><span class="secno">6.5.6.1 </span>event handlers</h5>
- </div><!--test: <a href="http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cscript%3E%0Aw(a%3Ddocument.implementation.createDocument(null%2C%20null%2C%20null))%3B%0Aw(a.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'html')))%3B%0Aw(b%3Da.firstChild.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'body')))%3B%0Aw(b.test%20%3D%20w)%3B%0Aw(b.setAttribute('onclick'%2C%20'test(%22fire%3A%20%22%20%2B%20event)'))%3B%0Aw(b.onclick)%3B%0Aw(e%3Da.createEvent('Event'))%3B%0Aw(e.initEvent('click'%2C%20false%2C%20false))%3B%0Aw(b.dispatchEvent(e))%3B%0A%3C%2Fscript%3E">test</a>--><p>Many objects can have <dfn id="event-handler-attributes-0">event handler attributes</dfn>
- specified. These act as bubbling event listeners for the object on
- which they are specified.<p>An <a href="#event-handler-attributes-0" title="event handler attributes">event handler
- attribute</a> can either have the value null or be set to a
- <code><a href="#function">Function</a></code> object. <span class="impl">Initially, event
- handler attributes must be set to null.</span><p>Event handler attributes are exposed in one or two ways.<p>The first way, common to all event handler attributes, is as an
- <a href="#event-handler-idl-attributes" title="event handler IDL attributes">event handler IDL
+ </div><!--test: <a href="http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cscript%3E%0Aw(a%3Ddocument.implementation.createDocument(null%2C%20null%2C%20null))%3B%0Aw(a.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'html')))%3B%0Aw(b%3Da.firstChild.appendChild(a.createElementNS('http%3A%2F%2Fwww.w3.org%2F1999%2Fxhtml'%2C%20'body')))%3B%0Aw(b.test%20%3D%20w)%3B%0Aw(b.setAttribute('onclick'%2C%20'test(%22fire%3A%20%22%20%2B%20event)'))%3B%0Aw(b.onclick)%3B%0Aw(e%3Da.createEvent('Event'))%3B%0Aw(e.initEvent('click'%2C%20false%2C%20false))%3B%0Aw(b.dispatchEvent(e))%3B%0A%3C%2Fscript%3E">test</a>--><p>Many objects can have <dfn id="event-handlers">event handlers</dfn> specified. These
+ act as bubbling event listeners for the object on which they are
+ specified.<p>An <a href="#event-handlers" title="event handlers">event handler</a> can either
+ have the value null or be set to a <code><a href="#function">Function</a></code>
+ object. <span class="impl">Initially, event handlers must be set to
+ null.</span><p>Event handlers are exposed in one or two ways.<p>The first way, common to all event handlers, is as an <a href="#event-handler-idl-attributes" title="event handler IDL attributes">event handler IDL
attribute</a>.<p>The second way is as an <a href="#event-handler-content-attributes" title="event handler content
- attributes">event handler content attribute</a>. Event handlers on
- <a href="#html-elements">HTML elements</a> and some of the event handlers on
+ attributes">event handler content attribute</a>. Event handlers
+ on <a href="#html-elements">HTML elements</a> and some of the event handlers on
<code><a href="#window">Window</a></code> objects are exposed in this way.<div class="impl">
<hr><p><dfn id="event-handler-idl-attributes">Event handler IDL attributes</dfn>, on setting, must set the
- corresponding event handler attribute to their new value, and on
+ corresponding event handler to their new value, and on
getting, must return whatever the current value of the corresponding
- event handler attribute is (possibly null).</p>
+ event handler is (possibly null).</p>
<p>If an <a href="#event-handler-idl-attributes" title="event handler IDL attributes">event handler
- IDL attribute</a> exposes an <a href="#event-handler-attributes-0" title="event handler
- attributes">event handler attribute</a> of an object that doesn't
- exist, it must always return null on getting and must do nothing on
- setting.</p>
+ IDL attribute</a> exposes an <a href="#event-handlers" title="event handlers">event
+ handler</a> of an object that doesn't exist, it must always
+ return null on getting and must do nothing on setting.</p>
<p class="note">This can happen in particular for <a href="#event-handler-idl-attributes" title="event
handler IDL attributes">event handler IDL attribute</a> on
@@ -45302,8 +45299,8 @@
</li>
<li><p>If the previous steps failed to compile the script, then set
- the corresponding <a href="#event-handler-attributes-0" title="event handler attributes">event
- handler attribute</a> to null and abort these steps.</li>
+ the corresponding <a href="#event-handlers" title="event handlers">event handler</a>
+ to null and abort these steps.</li>
<li><p>Set up the <a href="#script-s-global-object">script's global object</a>, the
<a href="#script-s-browsing-context">script's browsing context</a>, the <a href="#script-s-url-character-encoding">script's URL
@@ -45311,46 +45308,44 @@
from <a href="#the-script-settings-determined-from-the-node">the script settings determined from the node</a> on
which the attribute is being set.</li>
- <li><p>Set the corresponding <a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a>
- to the aforementioned function.</li>
+ <li><p>Set the corresponding <a href="#event-handlers" title="event handlers">event
+ handler</a> to the aforementioned function.</li>
</ol></div><p class="note">When an <a href="#event-handler-content-attributes" title="event handler content
attributes">event handler content attribute</a> is set on an
element owned by a <code>Document</code> that is not in a
- <a href="#browsing-context">browsing context</a>, the corresponding event handler
- attribute is not changed.<p class="note">Removing an <a href="#event-handler-content-attributes" title="event handler content
+ <a href="#browsing-context">browsing context</a>, the corresponding event handler is not changed.<p class="note">Removing an <a href="#event-handler-content-attributes" title="event handler content
attributes">event handler content attribute</a> does not reset
- the corresponding <a href="#event-handler-attributes-0" title="event handler attributes">event
- handler attribute</a>.</p><!--
+ the corresponding <a href="#event-handlers" title="event handlers">event
+ handler</a>.</p><!--
http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cbody%20onload%3D%22w(%27pass%27)%22%3E%0A%3Cscript%3Edocument.body.removeAttribute(%27onload%27)%3B%3C%2Fscript%3E
--><!-- v2: we should probably support HTML4's Content-Script-Type header here. --><div class="impl">
- <hr><p>All <a href="#event-handler-attributes-0">event handler attributes</a> on an element, whether
+ <hr><p>All <a href="#event-handlers">event handlers</a> on an element, whether
set to null or to a <code><a href="#function">Function</a></code> object, must be registered
as event listeners on the element, as if the <code title="dom-EventTarget-addEventListenerNS">addEventListenerNS()</code>
method on the <code>Element</code> object's <code>EventTarget</code>
- interface had been invoked when the event handler attribute's
+ interface had been invoked when the event handler's
element or object was created, with the event type (<var title="dom-event-type">type</var> argument) equal to the type
- corresponding to the event handler attribute (the <dfn id="event-handler-event-type">event handler
+ corresponding to the event handler (the <dfn id="event-handler-event-type">event handler
event type</dfn>), the namespace (<var title="dom-event-namespaceURI">namespaceURI</var> argument) set to
null, the listener set to be a target and bubbling phase listener
(<var title="dom-event-useCapture">useCapture</var> argument set to
false), the event group set to the default group (<var title="dom-event-evtGroup">evtGroup</var> argument set to null), and
the event listener itself (<var title="dom-event-listener">listener</var> argument) set to do
- nothing while the event handler attribute's value is not a
+ nothing while the event handler's value is not a
<code><a href="#function">Function</a></code> object, and set to invoke the <code title="dom-function-call"><a href="#dom-function-call">call()</a></code> callback of the
- <code><a href="#function">Function</a></code> object associated with the event handler
- attribute otherwise.</p>
+ <code><a href="#function">Function</a></code> object associated with the event handler otherwise.</p>
<p class="note">The <var title="dom-event-listener">listener</var>
- argument is emphatically <em>not</em> the <a href="#event-handler-attributes-0" title="event handler
- attributes">event handler attribute</a> itself.</p>
+ argument is emphatically <em>not</em> the <a href="#event-handlers" title="event
+ handlers">event handler</a> itself.</p>
<p class="note">The interfaces implemented by the event object do
- not affect whether an <a href="#event-handler-attributes-0" title="event handler attributes">event
- handler attribute</a> is used or not.</p>
+ not affect whether an <a href="#event-handlers" title="event handlers">event
+ handler</a> is used or not.</p>
- <p>When an <a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a>'s
+ <p>When an <a href="#event-handlers" title="event handlers">event handler</a>'s
<code><a href="#function">Function</a></code> object is invoked, its <code title="dom-function-call"><a href="#dom-function-call">call()</a></code> callback must be invoked
with one argument, set to the <code>Event</code> object of the event
in question.</p>
@@ -45391,16 +45386,16 @@
</div><div class="impl">
- <h5 id="event-handler-attributes-on-elements-document-objects-and-window-objects"><span class="secno">6.5.6.2 </span>Event handler attributes on elements, <code>Document</code> objects, and <code><a href="#window">Window</a></code> objects</h5>
+ <h5 id="event-handlers-on-elements-document-objects-and-window-objects"><span class="secno">6.5.6.2 </span>Event handlers on elements, <code>Document</code> objects, and <code><a href="#window">Window</a></code> objects</h5>
- <p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and
- their corresponding <a href="#event-handler-event-type" title="event handler event type">event
- handler event types</a>) that must be supported by all <a href="#html-elements">HTML
+ <p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported by all <a href="#html-elements">HTML
elements</a>, as both content attributes and IDL attributes, and
on <code>Document</code> and <code><a href="#window">Window</a></code> objects, as IDL
attributes.</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-onabort" title="handler-onabort"><code>onabort</code></dfn> <td> <code title="event-abort">abort</code>
<tr><td><dfn id="handler-oncanplay" title="handler-oncanplay"><code>oncanplay</code></dfn> <td> <code title="event-canplay">canplay</code>
<tr><td><dfn id="handler-oncanplaythrough" title="handler-oncanplaythrough"><code>oncanplaythrough</code></dfn> <td> <code title="event-canplaythrough">canplaythrough</code>
@@ -45458,27 +45453,26 @@
<!--<tr><td><dfn title="handler-onpaste"><code>onpaste</code></dfn> <td> <code title="event-paste">paste</code>--> <!-- widely used -->
<!-- not supported yet (v2?): -->
<!--<tr><td><dfn title="handler-onselectstart"><code>onselectstart</code></dfn> <td> <code title="event-selectstart">selectstart</code>--> <!-- widely used -->
- </table><hr><p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and
- their corresponding <a href="#event-handler-event-type" title="event handler event type">event
- handler event types</a>) that must be supported by all <a href="#html-elements">HTML
+ </table><hr><p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported by all <a href="#html-elements">HTML
elements</a> other than <code><a href="#the-body-element-0">body</a></code>, as both content
attributes and IDL attributes, and on <code>Document</code> objects,
as IDL attributes:</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-onblur" title="handler-onblur"><code>onblur</code></dfn> <td> <code title="event-blur">blur</code> <!-- widely used -->
<tr><td><dfn id="handler-onerror" title="handler-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
<tr><td><dfn id="handler-onfocus" title="handler-onfocus"><code>onfocus</code></dfn> <td> <code title="event-focus">focus</code> <!-- widely used -->
<tr><td><dfn id="handler-onload" title="handler-onload"><code>onload</code></dfn> <td> <code title="event-load">load</code>
- </table><hr><p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and
- their corresponding <a href="#event-handler-event-type" title="event handler event type">event
- handler event types</a>) that must be supported by
- <code><a href="#window">Window</a></code> objects, as IDL attributes on the
- <code><a href="#window">Window</a></code> object, and with corresponding content
- attributes and IDL attributes exposed on the <code><a href="#the-body-element-0">body</a></code> and
- <code><a href="#frameset">frameset</a></code> elements:</p>
+ </table><hr><p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported by <code><a href="#window">Window</a></code>
+ objects, as IDL attributes on the <code><a href="#window">Window</a></code> object, and
+ with corresponding content attributes and IDL attributes exposed on
+ the <code><a href="#the-body-element-0">body</a></code> and <code><a href="#frameset">frameset</a></code> elements:</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-window-onafterprint" title="handler-window-onafterprint"><code>onafterprint</code></dfn> <td> <code title="event-afterprint">afterprint</code>
<tr><td><dfn id="handler-window-onbeforeprint" title="handler-window-onbeforeprint"><code>onbeforeprint</code></dfn> <td> <code title="event-beforeprint">beforeprint</code>
<tr><td><dfn id="handler-window-onbeforeunload" title="handler-window-onbeforeunload"><code>onbeforeunload</code></dfn> <td> <code title="event-beforeunload">beforeunload</code>
@@ -45577,16 +45571,15 @@
<p>Whenever an uncaught runtime script error occurs in one of the
scripts associated with a <code>Document</code>, the user agent must
- <a href="#report-the-error">report the error</a> using the <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code> <a href="#event-handler-attributes-0" title="event
- handler attributes">event handler attribute</a> of the
- <a href="#script-s-global-object">script's global object</a>. If the error is still <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i> after this, then
+ <a href="#report-the-error">report the error</a> using the <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code> <a href="#event-handlers" title="event
+ handlers">event handler</a> of the <a href="#script-s-global-object">script's global
+ object</a>. If the error is still <i title="concept-error-nothandled"><a href="#concept-error-nothandled">not handled</a></i> after this, then
the error should be reported to the user.</p>
<hr><p>When the user agent is required to <dfn id="report-the-error" title="report the
error">report an error</dfn> <var title="">error</var> using the
- <a href="#event-handler-attributes-0" title="event handler attributes">event handler
- attribute</a> <var title="">onerror</var>, it must run these
- steps, after which the error is either <dfn id="concept-error-handled" title="concept-error-handled"><i>handled</i></dfn> or <dfn id="concept-error-nothandled" title="concept-error-nothandled"><i>not handled</i></dfn>:</p>
+ <a href="#event-handlers" title="event handlers">event handler</a> <var title="">onerror</var>, it must run these steps, after which the
+ error is either <dfn id="concept-error-handled" title="concept-error-handled"><i>handled</i></dfn> or <dfn id="concept-error-nothandled" title="concept-error-nothandled"><i>not handled</i></dfn>:</p>
<dl class="switch"><dt>If the value of <var title="">onerror</var> is a
<code><a href="#function">Function</a></code></dt>
@@ -48393,13 +48386,13 @@
<a href="#cache-host">cache host</a> from <var title="">cache</var> and instead
associate it with <var title="">new cache</var>.</li>
- </ol><p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and
- their corresponding <a href="#event-handler-event-type" title="event handler event type">event
- handler event types</a>) that must be supported, as IDL
- attributes, by all objects implementing the
- <code><a href="#applicationcache">ApplicationCache</a></code> interface:</p>
+ </ol><p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported, as IDL attributes, by
+ all objects implementing the <code><a href="#applicationcache">ApplicationCache</a></code>
+ interface:</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-appcache-onchecking" title="handler-appcache-onchecking"><code>onchecking</code></dfn> <td> <code title="event-appcache-checking"><a href="#event-appcache-checking">checking</a></code>
<tr><td><dfn id="handler-appcache-onerror" title="handler-appcache-onerror"><code>onerror</code></dfn> <td> <code title="event-appcache-error"><a href="#event-appcache-error">error</a></code>
<tr><td><dfn id="handler-appcache-onnoupdate" title="handler-appcache-onnoupdate"><code>onnoupdate</code></dfn> <td> <code title="event-appcache-noupdate"><a href="#event-appcache-noupdate">noupdate</a></code>
@@ -49116,8 +49109,8 @@
page.</p>
<p>In addition, a user agent could ignore calls to <code title="dom-history-pushState"><a href="#dom-history-pushstate">pushState()</a></code> that are invoked on
- a timer, or from event handlers that do not represent a clear user
- action, or that are invoked in rapid succession.</p>
+ a timer, or from event listeners that are not triggered in response
+ to a clear user action, or that are invoked in rapid succession.</p>
</div><h3 id="browsing-the-web"><span class="secno">6.11 </span>Browsing the Web</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><div class="impl">
@@ -53211,7 +53204,7 @@
<p>If it is not canceled, then the drag-and-drop operation must be
initiated.</p>
- <p class="note">Since events with no event handlers registered are,
+ <p class="note">Since events with no event listeners registered are,
almost by definition, never canceled, drag-and-drop is always
available to the user if the author does not specifically prevent
it.</p>
@@ -53262,7 +53255,7 @@
pointing device, or by selecting them in some other way). The
<a href="#current-target-element">current target element</a> changes when the <a href="#immediate-user-selection">immediate
user selection</a> changes, based on the results of event
- handlers in the document, as described below.</p>
+ listeners in the document, as described below.</p>
<p>Both the <a href="#current-target-element">current target element</a> and the
<a href="#immediate-user-selection">immediate user selection</a> can be null, which means no
@@ -54897,7 +54890,7 @@
void <a href="#dom-messageport-start" title="dom-MessagePort-start">start</a>();
void <a href="#dom-messageport-close" title="dom-MessagePort-close">close</a>();
- // event handler attributes
+ // event handlers
attribute <a href="#function">Function</a> <a href="#handler-messageport-onmessage" title="handler-MessagePort-onmessage">onmessage</a>;
};
<a href="#messageport">MessagePort</a> implements <span>EventTarget</span>;</pre><dl class="domintro"><!-- v2-onclose
@@ -55143,7 +55136,7 @@
source">task sources</a>.</p>
<p class="note">If the <code>Document</code> of the port's event
- handlers' <a href="#script-s-global-object" title="script's global object">global object</a>
+ listeners' <a href="#script-s-global-object" title="script's global object">global object</a>
is not <a href="#fully-active">fully active</a>, then the messages are lost.</p>
<!-- because of the jump-to-entry-point algorithm first step -->
@@ -55153,11 +55146,12 @@
disentangle the two ports. If the method is called on a port that is
not entangled, then the method must do nothing.</p>
- <hr><p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and their corresponding <a href="#event-handler-event-type" title="event handler event type">event handler event types</a>)
- that must be supported, as IDL attributes, by all objects
- implementing the <code><a href="#messageport">MessagePort</a></code> interface:</p>
+ <hr><p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported, as IDL attributes, by
+ all objects implementing the <code><a href="#messageport">MessagePort</a></code> interface:</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-messageport-onmessage" title="handler-MessagePort-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message"><a href="#event-message">message</a></code>
</table><p>The first time a <code><a href="#messageport">MessagePort</a></code> object's <code title="handler-MessagePort-onmessage"><a href="#handler-messageport-onmessage">onmessage</a></code> IDL attribute
is set, the port's <a href="#port-message-queue">port message queue</a> must be enabled,
@@ -67831,12 +67825,12 @@
</li>
- </ol><hr><p>The following are the <a href="#event-handler-attributes-0">event handler attributes</a> (and
- their corresponding <a href="#event-handler-event-type" title="event handler event type">event
- handler event types</a>) that must be supported, as content and
- IDL attributes, by <code><a href="#the-marquee-element">marquee</a></code> elements:</p>
+ </ol><hr><p>The following are the <a href="#event-handlers">event handlers</a> (and their
+ corresponding <a href="#event-handler-event-type" title="event handler event type">event handler
+ event types</a>) that must be supported, as content and IDL
+ attributes, by <code><a href="#the-marquee-element">marquee</a></code> elements:</p>
- <table><thead><tr><th><a href="#event-handler-attributes-0" title="event handler attributes">event handler attribute</a> <th><a href="#event-handler-event-type">Event handler event type</a>
+ <table><thead><tr><th><a href="#event-handlers" title="event handlers">Event handler</a> <th><a href="#event-handler-event-type">Event handler event type</a>
<tbody><tr><td><dfn id="handler-marquee-onbounce" title="handler-marquee-onbounce"><code>onbounce</code></dfn> <td> <code title="event-bounce">bounce</code>
<tr><td><dfn id="handler-marquee-onfinish" title="handler-marquee-onfinish"><code>onfinish</code></dfn> <td> <code title="event-finish">finish</code>
<tr><td><dfn id="handler-marquee-onstart" title="handler-marquee-onstart"><code>onstart</code></dfn> <td> <code title="event-start">start</code>
@@ -67898,8 +67892,7 @@
<p>The <code><a href="#frameset">frameset</a></code> element must support the following
<a href="#event-handler-content-attributes">event handler content attributes</a> exposing the
- <a href="#event-handler-attributes-0">event handler attributes</a> of the <code><a href="#window">Window</a></code>
- object:</p>
+ <a href="#event-handlers">event handlers</a> of the <code><a href="#window">Window</a></code> object:</p>
<ul class="brief"><li><code title="handler-window-onafterprint"><a href="#handler-window-onafterprint">onafterprint</a></code></li>
<li><code title="handler-window-onbeforeprint"><a href="#handler-window-onbeforeprint">onbeforeprint</a></code></li>
@@ -67922,11 +67915,11 @@
attributes</a> that mirror those on the <code><a href="#window">Window</a></code>
element.</p>
- <p>The <code title="handler-window-onblur"><a href="#handler-window-onblur">onblur</a></code>, <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code>, <code title="handler-window-onfocus"><a href="#handler-window-onfocus">onfocus</a></code>, and <code title="handler-window-onload"><a href="#handler-window-onload">onload</a></code> <a href="#event-handler-attributes-0">event handler
+ <p>The <code title="handler-window-onblur"><a href="#handler-window-onblur">onblur</a></code>, <code title="handler-window-onerror"><a href="#handler-window-onerror">onerror</a></code>, <code title="handler-window-onfocus"><a href="#handler-window-onfocus">onfocus</a></code>, and <code title="handler-window-onload"><a href="#handler-window-onload">onload</a></code> <a href="#event-handler-idl-attributes">event handler IDL
attributes</a> of the <code><a href="#window">Window</a></code> object, exposed on the
- <code><a href="#frameset">frameset</a></code> element, shadow the generic <a href="#event-handler-attributes-0">event
- handler attributes</a> with the same names normally supported by
- <a href="#html-elements">HTML elements</a>.</p>
+ <code><a href="#frameset">frameset</a></code> element, shadow the generic <a href="#event-handler-idl-attributes">event
+ handler IDL attributes</a> with the same names normally supported
+ by <a href="#html-elements">HTML elements</a>.</p>
<hr><p>The <dfn id="frame"><code>frame</code></dfn> element defines a <a href="#nested-browsing-context">nested
browsing context</a> similar to the <code><a href="#the-iframe-element">iframe</a></code> element,
Received on Tuesday, 29 September 2009 00:32:56 UTC