[html5] r4013 - [e] (0) Rename 'event handler attributes' to 'event handlers' to reduce confusio [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Sep 28 17:40:12 PDT 2009
Author: ianh
Date: 2009-09-28 17:40:11 -0700 (Mon, 28 Sep 2009)
New Revision: 4013
Modified:
index
source
Log:
[e] (0) Rename 'event handler attributes' to 'event handlers' to reduce confusion with the actual attributes.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7625
Modified: index
===================================================================
--- index 2009-09-29 00:22:04 UTC (rev 4012)
+++ index 2009-09-29 00:40:11 UTC (rev 4013)
@@ -697,8 +697,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>
@@ -7708,7 +7708,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.</p>
<hr><p><a href=#custom-data-attribute title="custom data attribute">Custom data attributes</a>
@@ -12908,15 +12908,15 @@
</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
+ 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>
- <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>
+ <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>
<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
@@ -12927,10 +12927,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.</p>
@@ -19909,10 +19909,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>
@@ -50219,44 +50218,42 @@
<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>
+ <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>
- <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>
+ <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>
- <p>Event handler attributes are exposed in one or two ways.</p>
+ <p>Event handlers are exposed in one or two ways.</p>
- <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
+ <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>
<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.</p>
<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
@@ -50315,8 +50312,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
@@ -50324,21 +50321,20 @@
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>
+ <a href=#browsing-context>browsing context</a>, the corresponding event handler is not changed.</p>
<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
-->
@@ -50346,32 +50342,31 @@
<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>
@@ -50415,16 +50410,16 @@
<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>
@@ -50482,27 +50477,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>
@@ -50610,16 +50604,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>
@@ -53622,13 +53615,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>
@@ -54435,8 +54428,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>
@@ -59144,7 +59137,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>
@@ -59195,7 +59188,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
@@ -60979,7 +60972,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>
@@ -61227,7 +61220,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 -->
@@ -61237,11 +61230,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,
@@ -74336,12 +74330,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>
@@ -74403,8 +74397,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>
@@ -74427,11 +74420,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,
Modified: source
===================================================================
--- source 2009-09-29 00:22:04 UTC (rev 4012)
+++ source 2009-09-29 00:40:11 UTC (rev 4013)
@@ -7778,7 +7778,7 @@
<p class="note">The attributes marked with an asterisk have a
different meaning when specified on <code>body</code> elements as
- those elements expose <span>event handler attributes</span> of the
+ those elements expose <span>event handlers</span> of the
<code>Window</code> object with the same names.</p>
<hr>
@@ -13736,18 +13736,18 @@
</div>
<p>The <code>body</code> element exposes as <span>event handler
- content attributes</span> a number of the <span>event handler
- attributes</span> of the <code>Window</code> object. It also mirrors
+ content attributes</span> a number of the <span>event
+ handlers</span> of the <code>Window</code> object. It also mirrors
their <span>event handler IDL attributes</span>.</p>
<p>The <code title="handler-window-onblur">onblur</code>, <code
title="handler-window-onerror">onerror</code>, <code
title="handler-window-onfocus">onfocus</code>, and <code
- title="handler-window-onload">onload</code> <span>event handler
- attributes</span> of the <code>Window</code> object, exposed on the
- <code>body</code> element, shadow the generic <span>event handler
- attributes</span> with the same names normally supported by
- <span>HTML elements</span>.</p>
+ title="handler-window-onload">onload</code> <span>event
+ handlers</span> of the <code>Window</code> object, exposed on the
+ <code>body</code> element, shadow the generic <span>event
+ handlers</span> with the same names normally supported by <span>HTML
+ elements</span>.</p>
<p class="example">Thus, for example, a bubbling <code
title="event-error">error</code> event fired on a child of <span>the
@@ -13760,10 +13760,10 @@
attribute</span> on the <code>body</code> element. This is because
the event would bubble from the target, to the <code>body</code>, to
the <code>html</code>, to the <code>Document</code>, to the
- <code>Window</code>, and the <span title="event handler
- attributes">event handler attribute</span> on the <code>body</code>
- is watching the <code>Window</code> not the <code>body</code>. A
- regular event listener attached to the <code>body</code> using <code
+ <code>Window</code>, and the <span title="event handlers">event
+ handler</span> on the <code>body</code> is watching the
+ <code>Window</code> not the <code>body</code>. A regular event
+ listener attached to the <code>body</code> using <code
title="">addEventListener()</code>, however, would fire when the
event bubbled through the <code>body</code> and not when it reaches
the <code>Window</code> object.</p>
@@ -21337,10 +21337,9 @@
title="attr-iframe-sandbox">sandbox</code> attribute is
dynamically added after the <code>iframe</code> has loaded a page,
scripts already compiled by that page (whether in
- <code>script</code> elements, or in <span>event handler
- attributes</span>, or elsewhere) will continue to run. Only
- <em>new</em> scripts will be prevented from executing by this
- flag.</p>
+ <code>script</code> elements, or in <span>event handlers</span>,
+ or elsewhere) will continue to run. Only <em>new</em> scripts will
+ be prevented from executing by this flag.</p>
</dd>
@@ -56712,30 +56711,30 @@
<div class="impl">
- <h5 id="event-handler-attributes">Event handler attributes</h5>
+ <h5 id="event-handler-attributes">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>event handler attributes</dfn>
- specified. These act as bubbling event listeners for the object on
- which they are specified.</p>
+ <p>Many objects can have <dfn>event handlers</dfn> specified. These
+ act as bubbling event listeners for the object on which they are
+ specified.</p>
- <p>An <span title="event handler attributes">event handler
- attribute</span> can either have the value null or be set to a
- <code>Function</code> object. <span class="impl">Initially, event
- handler attributes must be set to null.</span></p>
+ <p>An <span title="event handlers">event handler</span> can either
+ have the value null or be set to a <code>Function</code>
+ object. <span class="impl">Initially, event handlers must be set to
+ null.</span></p>
- <p>Event handler attributes are exposed in one or two ways.</p>
+ <p>Event handlers are exposed in one or two ways.</p>
- <p>The first way, common to all event handler attributes, is as an
- <span title="event handler IDL attributes">event handler IDL
+ <p>The first way, common to all event handlers, is as an <span
+ title="event handler IDL attributes">event handler IDL
attribute</span>.</p>
<p>The second way is as an <span title="event handler content
- attributes">event handler content attribute</span>. Event handlers on
- <span>HTML elements</span> and some of the event handlers on
+ attributes">event handler content attribute</span>. Event handlers
+ on <span>HTML elements</span> and some of the event handlers on
<code>Window</code> objects are exposed in this way.</p>
<div class="impl">
@@ -56743,15 +56742,14 @@
<hr>
<p><dfn>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 <span title="event handler IDL attributes">event handler
- IDL attribute</span> exposes an <span title="event handler
- attributes">event handler attribute</span> of an object that doesn't
- exist, it must always return null on getting and must do nothing on
- setting.</p>
+ IDL attribute</span> exposes an <span title="event handlers">event
+ handler</span> 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 <span title="event
handler IDL attributes">event handler IDL attribute</span> on
@@ -56827,8 +56825,8 @@
</li>
<li><p>If the previous steps failed to compile the script, then set
- the corresponding <span title="event handler attributes">event
- handler attribute</span> to null and abort these steps.</p></li>
+ the corresponding <span title="event handlers">event handler</span>
+ to null and abort these steps.</p></li>
<li><p>Set up the <span>script's global object</span>, the
<span>script's browsing context</span>, the <span>script's URL
@@ -56836,8 +56834,8 @@
from <span>the script settings determined from the node</span> on
which the attribute is being set.</p></li>
- <li><p>Set the corresponding <span title="event handler attributes">event handler attribute</span>
- to the aforementioned function.</p></li>
+ <li><p>Set the corresponding <span title="event handlers">event
+ handler</span> to the aforementioned function.</p></li>
</ol>
@@ -56846,13 +56844,12 @@
<p class="note">When an <span title="event handler content
attributes">event handler content attribute</span> is set on an
element owned by a <code>Document</code> that is not in a
- <span>browsing context</span>, the corresponding event handler
- attribute is not changed.</p>
+ <span>browsing context</span>, the corresponding event handler is not changed.</p>
<p class="note">Removing an <span title="event handler content
attributes">event handler content attribute</span> does not reset
- the corresponding <span title="event handler attributes">event
- handler attribute</span>.</p> <!--
+ the corresponding <span title="event handlers">event
+ handler</span>.</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
-->
@@ -56862,15 +56859,15 @@
<hr>
- <p>All <span>event handler attributes</span> on an element, whether
+ <p>All <span>event handlers</span> on an element, whether
set to null or to a <code>Function</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>event handler
+ corresponding to the event handler (the <dfn>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
@@ -56879,21 +56876,20 @@
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>Function</code> object, and set to invoke the <code
title="dom-function-call">call()</code> callback of the
- <code>Function</code> object associated with the event handler
- attribute otherwise.</p>
+ <code>Function</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 <span title="event handler
- attributes">event handler attribute</span> itself.</p>
+ argument is emphatically <em>not</em> the <span title="event
+ handlers">event handler</span> itself.</p>
<p class="note">The interfaces implemented by the event object do
- not affect whether an <span title="event handler attributes">event
- handler attribute</span> is used or not.</p>
+ not affect whether an <span title="event handlers">event
+ handler</span> is used or not.</p>
- <p>When an <span title="event handler attributes">event handler attribute</span>'s
+ <p>When an <span title="event handlers">event handler</span>'s
<code>Function</code> object is invoked, its <code
title="dom-function-call">call()</code> callback must be invoked
with one argument, set to the <code>Event</code> object of the event
@@ -56947,18 +56943,18 @@
<div class="impl">
- <h5>Event handler attributes on elements, <code>Document</code> objects, and <code>Window</code> objects</h5>
+ <h5>Event handlers on elements, <code>Document</code> objects, and <code>Window</code> objects</h5>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported by all <span>HTML
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported by all <span>HTML
elements</span>, as both content attributes and IDL attributes, and
on <code>Document</code> and <code>Window</code> objects, as IDL
attributes.</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-onabort"><code>onabort</code></dfn> <td> <code title="event-abort">abort</code>
<tr><td><dfn title="handler-oncanplay"><code>oncanplay</code></dfn> <td> <code title="event-canplay">canplay</code>
@@ -57021,16 +57017,16 @@
<hr>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported by all <span>HTML
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported by all <span>HTML
elements</span> other than <code>body</code>, as both content
attributes and IDL attributes, and on <code>Document</code> objects,
as IDL attributes:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-onblur"><code>onblur</code></dfn> <td> <code title="event-blur">blur</code> <!-- widely used -->
<tr><td><dfn title="handler-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
@@ -57040,17 +57036,16 @@
<hr>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported by
- <code>Window</code> objects, as IDL attributes on the
- <code>Window</code> object, and with corresponding content
- attributes and IDL attributes exposed on the <code>body</code> and
- <code>frameset</code> elements:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported by <code>Window</code>
+ objects, as IDL attributes on the <code>Window</code> object, and
+ with corresponding content attributes and IDL attributes exposed on
+ the <code>body</code> and <code>frameset</code> elements:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-window-onafterprint"><code>onafterprint</code></dfn> <td> <code title="event-afterprint">afterprint</code>
<tr><td><dfn title="handler-window-onbeforeprint"><code>onbeforeprint</code></dfn> <td> <code title="event-beforeprint">beforeprint</code>
@@ -57188,8 +57183,8 @@
scripts associated with a <code>Document</code>, the user agent must
<span>report the error</span> using the <code
title="handler-window-onerror">onerror</code> <span title="event
- handler attributes">event handler attribute</span> of the
- <span>script's global object</span>. If the error is still <i
+ handlers">event handler</span> of the <span>script's global
+ object</span>. If the error is still <i
title="concept-error-nothandled">not handled</i> after this, then
the error should be reported to the user.</p>
@@ -57197,9 +57192,9 @@
<p>When the user agent is required to <dfn title="report the
error">report an error</dfn> <var title="">error</var> using the
- <span title="event handler attributes">event handler
- attribute</span> <var title="">onerror</var>, it must run these
- steps, after which the error is either <dfn
+ <span title="event handlers">event handler</span> <var
+ title="">onerror</var>, it must run these steps, after which the
+ error is either <dfn
title="concept-error-handled"><i>handled</i></dfn> or <dfn
title="concept-error-nothandled"><i>not handled</i></dfn>:</p>
@@ -60677,15 +60672,15 @@
</ol>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported, as IDL
- attributes, by all objects implementing the
- <code>ApplicationCache</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ all objects implementing the <code>ApplicationCache</code>
+ interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-appcache-onchecking"><code>onchecking</code></dfn> <td> <code title="event-appcache-checking">checking</code>
<tr><td><dfn title="handler-appcache-onerror"><code>onerror</code></dfn> <td> <code title="event-appcache-error">error</code>
@@ -61633,8 +61628,8 @@
<p>In addition, a user agent could ignore calls to <code
title="dom-history-pushState">pushState()</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>
@@ -68984,7 +68979,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>
@@ -69045,7 +69040,7 @@
pointing device, or by selecting them in some other way). The
<span>current target element</span> changes when the <span>immediate
user selection</span> 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 <span>current target element</span> and the
<span>immediate user selection</span> can be null, which means no
@@ -70543,8 +70538,7 @@
creates a worker and returns a <code>Worker</code> object
representing that worker, which is used to communicate with the
worker. That object's <code
- title="handler-Worker-onmessage">onmessage</code> event handler
- attribute allows the code to receive messages from the worker.</p>
+ title="handler-Worker-onmessage">onmessage</code> event handler allows the code to receive messages from the worker.</p>
<p>The worker itself is as follows:</p>
@@ -70848,14 +70842,15 @@
</ol>
- <p>The following are the <span>event handler attributes</span> (and their corresponding <span
- title="event handler event type">event handler event types</span>)
- that must be supported, as IDL attributes, by objects implementing
- the <code>WorkerGlobalScope</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ objects implementing the <code>WorkerGlobalScope</code>
+ interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<!-- v2-onclose <tr><td><dfn title="handler-WorkerGlobalScope-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
<tr><td><dfn title="handler-WorkerGlobalScope-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
@@ -70890,15 +70885,15 @@
method of the same name on the port, with the same arguments, and
returned the same return value.</p>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported, as IDL
- attributes, by objects implementing the
- <code>DedicatedWorkerGlobalScope</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ objects implementing the <code>DedicatedWorkerGlobalScope</code>
+ interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-DedicatedWorkerGlobalScope-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
</table>
@@ -70930,15 +70925,15 @@
that can be used to obtain a reference to the worker using the
<code>SharedWorker</code> constructor.</p>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported, as IDL
- attributes, by objects implementing the
- <code>SharedWorkerGlobalScope</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ objects implementing the <code>SharedWorkerGlobalScope</code>
+ interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-SharedWorkerGlobalScope-onconnect"><code>onconnect</code></dfn> <td> <code title="event-connect">connect</code>
</table>
@@ -71557,14 +71552,14 @@
};
<span>AbstractWorker</span> implements <span>EventTarget</span>;</pre>
- <p>The following are the <span>event handler attributes</span> (and their corresponding <span
- title="event handler event type">event handler event types</span>)
- that must be supported, as IDL attributes, by objects implementing
- the <code>AbstractWorker</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ objects implementing the <code>AbstractWorker</code> interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-AbstractWorker-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
<!-- v2-onclose <tr><td><dfn title="handler-AbstractWorker-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code> -->
@@ -71607,14 +71602,14 @@
immediately invoked the method of the same name on the port, with
the same arguments, and returned the same return value.</p>
- <p>The following are the <span>event handler attributes</span> (and their corresponding <span
- title="event handler event type">event handler event types</span>)
- that must be supported, as IDL attributes, by objects implementing
- the <code>Worker</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ objects implementing the <code>Worker</code> interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-Worker-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
</table>
@@ -72479,14 +72474,14 @@
<code title="dom-EventSource-CLOSED">CLOSED</code>. If the
connection is already closed, the method must do nothing.</p>
- <p>The following are the <span>event handler attributes</span> (and their corresponding <span
- title="event handler event type">event handler event types</span>)
- that must be supported, as IDL attributes, by all objects
- implementing the <code>EventSource</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ all objects implementing the <code>EventSource</code> interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-EventSource-onopen"><code>onopen</code></dfn> <td> <code title="event-open">open</code>
<tr><td><dfn title="handler-EventSource-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
@@ -73296,13 +73291,13 @@
<hr>
- <p>The following are the <span>event handler attributes</span> that
- must be supported, as IDL attributes, by all objects implementing
- the <code>WebSocket</code> interface:</p>
+ <p>The following are the <span>event handlers</span> that must be
+ supported, as IDL attributes, by all objects implementing the
+ <code>WebSocket</code> interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-WebSocket-onopen"><code>onopen</code></dfn> <td> <code title="event-open">open</code>
<tr><td><dfn title="handler-WebSocket-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
@@ -75486,7 +75481,7 @@
void <span title="dom-MessagePort-start">start</span>();
void <span title="dom-MessagePort-close">close</span>();
- // event handler attributes
+ // event handlers
attribute <span>Function</span> <span title="handler-MessagePort-onmessage">onmessage</span>;
};
<span>MessagePort</span> implements <span>EventTarget</span>;</pre>
@@ -75783,7 +75778,7 @@
source">task sources</span>.</p>
<p class="note">If the <code>Document</code> of the port's event
- handlers' <span title="script's global object">global object</span>
+ listeners' <span title="script's global object">global object</span>
is not <span>fully active</span>, then the messages are lost.</p>
<!-- because of the jump-to-entry-point algorithm first step -->
@@ -75797,14 +75792,14 @@
<hr>
- <p>The following are the <span>event handler attributes</span> (and their corresponding <span
- title="event handler event type">event handler event types</span>)
- that must be supported, as IDL attributes, by all objects
- implementing the <code>MessagePort</code> interface:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as IDL attributes, by
+ all objects implementing the <code>MessagePort</code> interface:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-MessagePort-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
</table>
@@ -88220,14 +88215,14 @@
<hr>
- <p>The following are the <span>event handler attributes</span> (and
- their corresponding <span title="event handler event type">event
- handler event types</span>) that must be supported, as content and
- IDL attributes, by <code>marquee</code> elements:</p>
+ <p>The following are the <span>event handlers</span> (and their
+ corresponding <span title="event handler event type">event handler
+ event types</span>) that must be supported, as content and IDL
+ attributes, by <code>marquee</code> elements:</p>
<table>
<thead>
- <tr><th><span title="event handler attributes">event handler attribute</span> <th><span>Event handler event type</span>
+ <tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-marquee-onbounce"><code>onbounce</code></dfn> <td> <code title="event-bounce">bounce</code>
<tr><td><dfn title="handler-marquee-onfinish"><code>onfinish</code></dfn> <td> <code title="event-finish">finish</code>
@@ -88307,8 +88302,7 @@
<p>The <code>frameset</code> element must support the following
<span>event handler content attributes</span> exposing the
- <span>event handler attributes</span> of the <code>Window</code>
- object:</p>
+ <span>event handlers</span> of the <code>Window</code> object:</p>
<ul class="brief">
<li><code title="handler-window-onafterprint">onafterprint</code></li>
@@ -88337,11 +88331,11 @@
<p>The <code title="handler-window-onblur">onblur</code>, <code
title="handler-window-onerror">onerror</code>, <code
title="handler-window-onfocus">onfocus</code>, and <code
- title="handler-window-onload">onload</code> <span>event handler
+ title="handler-window-onload">onload</code> <span>event handler IDL
attributes</span> of the <code>Window</code> object, exposed on the
<code>frameset</code> element, shadow the generic <span>event
- handler attributes</span> with the same names normally supported by
- <span>HTML elements</span>.</p>
+ handler IDL attributes</span> with the same names normally supported
+ by <span>HTML elements</span>.</p>
<hr>
More information about the Commit-Watchers
mailing list