- From: poot <cvsmail@w3.org>
- Date: Sat, 13 Sep 2008 10:07:23 +0900 (JST)
- To: public-html-diffs@w3.org
WF2: form.reset() and a rework of how we categorise form control
elements. (whatwg r2175)
Resettable elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#resettable
input
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#input0
tasks
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#tasks
associated
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#associated
7. Communication
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#comms
When the user agent is required to dispatch the event, then the user agent must act as follows:
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#dispatchMessage
4.10 Scripting
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#scripting1
3.3.3 Global attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#global
HTMLFormElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#htmlformelement
dispatch a formchange event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#dispatch
task queues
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#task-queues
accept-charset
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#accept-charset
in table
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#in-table
The steps to process the field given a field name and a field value depend on the field name, as given in the following list. Field names must be compared literally, with no case folding performed.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#processField
swapCache()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#swapcache
elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#elements3
elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#elements4
4.9.18 Event dispatch
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event
select
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#select
with script
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#with-script
4.9.1 The form element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#the-form
start()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#start6
Event handler DOM attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event7
submit()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#submit
5.4.3 Security exceptions
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#security4
buttons
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#buttons
Window
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#window
effective script origin
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#effective3
Listed
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#listed
4.9.2 The fieldset element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#the-fieldset
secondary insertion mode
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#secondary1
HTMLFormControlsCollection
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#htmlformcontrolscollection0
StorageEvent
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#storageevent
event loops
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event4
fieldset
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#fieldset
HTMLElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#htmlelement
form
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#form
fragment case
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#fragment
storage
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#storage1
text/plain encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#textplain
unselect
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#unselect
5.10.1.6. Threads
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#threads
If form is in a Document that has no associated browsing context or whose browsing context has its sandboxed forms browsing context flag set, then abort these steps without doing anything.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#sandboxSubmitBlocked
reset
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#reset1
reset the form owner
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#reset0
reset the insertion mode appropriately
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#reset3
reset algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#reset2
2.8.2.2. HTMLFormControlsCollection
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#htmlformcontrolscollection
reset()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#reset
close()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#close3
onunload
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#onunload
close
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#close1
textarea
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#textarea
5.10.1.5.1. Event definition
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event2
button
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#button
4.9.3 The input element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#the-input
Submittable elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#submittable
queue a task
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#queue
in select
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#in-select
task source
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#task-source
5.4.2 Event loops
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event0
5.4.5.1. Event handler attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event-handler-attributes
Event handler content attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event6
output
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#output
form-associated elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#form-associated
event handler attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event5
4.9.17 Resetting a form
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#resetting
7.1 Event definitions
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event3
5.4 Scripting
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#scripting
5.4.5.2. Event firing
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1348.html#event1
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1347&r2=1.1348&f=h
http://html5.org/tools/web-apps-tracker?from=2174&to=2175
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1347
retrieving revision 1.1348
diff -u -d -r1.1347 -r1.1348
--- Overview.html 13 Sep 2008 00:36:36 -0000 1.1347
+++ Overview.html 13 Sep 2008 01:03:47 -0000 1.1348
@@ -1091,6 +1091,12 @@
<li><a href="#plain"><span class=secno>4.9.16.3. </span>Plain text
form data</a>
</ul>
+
+ <li><a href="#resetting"><span class=secno>4.9.17 </span>Resetting a
+ form</a>
+
+ <li><a href="#event"><span class=secno>4.9.18 </span>Event
+ dispatch</a>
</ul>
<li><a href="#scripting1"><span class=secno>4.10 </span>Scripting</a>
@@ -1310,7 +1316,7 @@
<li><a href="#script0"><span class=secno>5.4.1 </span>Script execution
contexts</a>
- <li><a href="#event"><span class=secno>5.4.2 </span>Event loops</a>
+ <li><a href="#event0"><span class=secno>5.4.2 </span>Event loops</a>
<li><a href="#security4"><span class=secno>5.4.3 </span>Security
exceptions</a>
@@ -1323,7 +1329,7 @@
<li><a href="#event-handler-attributes"><span class=secno>5.4.5.1.
</span>Event handler attributes</a>
- <li><a href="#event0"><span class=secno>5.4.5.2. </span>Event
+ <li><a href="#event1"><span class=secno>5.4.5.2. </span>Event
firing</a>
<li><a href="#events0"><span class=secno>5.4.5.3. </span>Events and
@@ -1485,7 +1491,7 @@
<li><a href="#the-storage0"><span class=secno>5.10.1.5. </span>The
<code title=event-storage>storage</code> event</a>
<ul class=toc>
- <li><a href="#event1"><span class=secno>5.10.1.5.1. </span>Event
+ <li><a href="#event2"><span class=secno>5.10.1.5.1. </span>Event
definition</a>
</ul>
@@ -1754,7 +1760,7 @@
<li><a href="#comms"><span class=secno>7. </span>Communication</a>
<ul class=toc>
- <li><a href="#event2"><span class=secno>7.1 </span>Event definitions</a>
+ <li><a href="#event3"><span class=secno>7.1 </span>Event definitions</a>
<li><a href="#server-sent-events"><span class=secno>7.2
@@ -6746,8 +6752,10 @@
<p>The <code><a
href="#htmlformcontrolscollection0">HTMLFormControlsCollection</a></code>
interface represents a <a href="#collections0"
- title=collections>collection</a> of <a href="#field"
- title=category-field>field elements</a>.
+ title=collections>collection</a> of <a href="#listed"
+ title=category-listed>listed</a> elements in <code><a
+ href="#form">form</a></code> and <code><a
+ href="#fieldset">fieldset</a></code> elements.
<pre
class=idl>interface <dfn id=htmlformcontrolscollection0>HTMLFormControlsCollection</dfn> {
@@ -7795,7 +7803,7 @@
attribute DOMString <a href="#registrationmark0" title=dom-registrationMark>registrationMark</a>;
readonly attribute DocumentFragment <a href="#originalcontent" title=dom-originalContent>originalContent</a>;
- // <a href="#event6">event handler DOM attributes</a>
+ // <a href="#event7">event handler DOM attributes</a>
attribute <span>EventListener</span> <a href="#onabort" title=handler-onabort>onabort</a>;
attribute <span>EventListener</span> <a href="#onbeforeunload" title=handler-onbeforeunload>onbeforeunload</a>;
attribute <span>EventListener</span> <a href="#onblur" title=handler-onblur>onblur</a>;
@@ -7879,7 +7887,7 @@
<dd><code title=attr-title><a href="#title">title</a></code>
</dl>
- <p>In addition, the following <a href="#event5">event handler content
+ <p>In addition, the following <a href="#event6">event handler content
attributes</a> may be specified on any <span>HTML element</span>:
<dl class=element>
@@ -26547,20 +26555,36 @@
content attribute with a matching <code title=dom-fae-form><a
href="#form1">form</a></code> DOM attribute.
- <p>The controls that can end up being submitted back to the server are <dfn
- id=field title=category-field>field elements</dfn>.
+ <p>The <a href="#form-associated" title="form-associated
+ element">form-associated elements</a> fall into several subcategories:
- <p>The controls that are exposed to the <code title=dom-form-elements><a
- href="#elements3"><var title="">form</var>.elements</a></code> and <code
- title=dom-fieldset-elements><a href="#elements4"><var
- title="">fieldset</var>.elements</a></code> APIs are <dfn id=listed
- title=category-listed-form-element>listed form elements</dfn>. This is a
- superset of the <a href="#field" title=category-field>field elements</a>.
+ <dl>
+ <dt><dfn id=submittable title=category-submit>Submittable elements</dfn>
- <p>Some <a href="#field" title=category-field>field elements</a> can be,
- depending on their attributes, <dfn id=buttons
- title=concept-button>buttons</dfn>. The prose below defines when an
- element is a button.
+ <dd>Denotes elements that can be used for <a
+ href="#constructing-form-data-set">constructing the form data set</a>
+ when a <code><a href="#form">form</a></code> element is <a
+ href="#submitted" title=concept-form-submit>submit</a>.
+
+ <dt><dfn id=resettable title=category-reset>Resettable elements</dfn>
+
+ <dd>Denotes elements that can be affected when a <code><a
+ href="#form">form</a></code> element is <a href="#reset1"
+ title=concept-form-reset>reset</a>.
+
+ <dt><dfn id=listed title=category-listed>Listed</dfn>
+
+ <dd>Denotes elements that are listed in the <code
+ title=dom-form-elements><a href="#elements3"><var
+ title="">form</var>.elements</a></code> and <code
+ title=dom-fieldset-elements><a href="#elements4"><var
+ title="">fieldset</var>.elements</a></code> APIs.
+ </dl>
+
+ <p>In addition, some <a href="#submittable"
+ title=category-submit>submittable</a> can be, depending on their
+ attributes, <dfn id=buttons title=concept-button>buttons</dfn>. The prose
+ below defines when an element is a button.
<h4 id=the-form><span class=secno>4.9.1 </span>The <dfn
id=form><code>form</code></dfn> element</h4>
@@ -26612,7 +26636,7 @@
[NameGetter] Object <a href="#xxx8" title=dom-form-XXX8>XXX8</a>(in DOMString name);
void <a href="#submit" title=dom-form-submit>submit</a>();
- void <span title=dom-form-reset>reset</span>();
+ void <a href="#reset" title=dom-form-reset>reset</a>();
boolean <span title=dom-form-checkValidity>checkValidity</span>();
void <span title=dom-form-dispatchFormInput>dispatchFormInput</span>();
@@ -26621,8 +26645,9 @@
</dl>
<p>The <code><a href="#form">form</a></code> element represents a
- collection of <a href="#field" title=category-field>data fields</a> that
- can be submitted to a server for processing.
+ collection of <a href="#form-associated" title="form-associated
+ element">form-associated elements</a>, some of which can represent
+ editable values that can be submitted to a server for processing.
<p>The <dfn id=accept-charset
title=attr-form-accept-charset><code>accept-charset</code></dfn> attribute
@@ -26655,8 +26680,8 @@
return an <code><a
href="#htmlformcontrolscollection0">HTMLFormControlsCollection</a></code>
rooted at the <code>Document</code> node, whose filter matches <a
- href="#listed" title=category-listed-form-element>listed form elements</a>
- whose <a href="#form-owner">form owner</a> is the <code><a
+ href="#listed" title=category-listed>listed</a> elements whose <a
+ href="#form-owner">form owner</a> is the <code><a
href="#form">form</a></code> element, with the exception of <code><a
href="#input0">input</a></code> elements whose <code
title=attr-input-type>type</code> attribute is in the <span
@@ -26692,6 +26717,11 @@
href="#form">form</a></code> element from the <code><a
href="#form">form</a></code> element itself.
+ <p>The <dfn id=reset title=dom-form-reset><code>reset()</code></dfn>
+ method, when invoked, must <a href="#reset1"
+ title=concept-form-reset>reset</a> the <code><a
+ href="#form">form</a></code> element.
+
<p class=big-issue>...
<h4 id=the-fieldset><span class=secno>4.9.2 </span>The <dfn
@@ -26702,10 +26732,8 @@
<dd><a href="#flow-content0">Flow content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -26751,9 +26779,8 @@
return an <code><a
href="#htmlformcontrolscollection0">HTMLFormControlsCollection</a></code>
rooted at the <code>Document</code> node, whose filter matches <a
- href="#listed" title=category-listed-form-element>listed form elements</a>
- that are descendants of the <code><a href="#fieldset">fieldset</a></code>
- element.
+ href="#listed" title=category-listed>listed</a> elements that are
+ descendants of the <code><a href="#fieldset">fieldset</a></code> element.
<h4 id=the-input><span class=secno>4.9.3 </span>The <dfn
id=input0><code>input</code></dfn> element</h4>
@@ -26765,12 +26792,10 @@
<dd><a href="#interactive1">Interactive content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#field" title=category-field>Field element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a>, <a
+ href="#submittable" title=category-submit>submittable</a>, and <a
+ href="#resettable" title=category-reset>resettable</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -26906,12 +26931,9 @@
<dd><a href="#interactive1">Interactive content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#field" title=category-field>Field element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a> and <a
+ href="#submittable" title=category-submit>submittable</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -27020,12 +27042,10 @@
<dd><a href="#interactive1">Interactive content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#field" title=category-field>Field element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a>, <a
+ href="#submittable" title=category-submit>submittable</a>, and <a
+ href="#resettable" title=category-reset>resettable</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -27234,12 +27254,10 @@
<dd><a href="#interactive1">Interactive content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#field" title=category-field>Field element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a>, <a
+ href="#submittable" title=category-submit>submittable</a>, and <a
+ href="#resettable" title=category-reset>resettable</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -27324,10 +27342,9 @@
<dd><a href="#phrasing0">Phrasing content</a>.
- <dd><a href="#form-associated">Form-associated element</a>.
-
- <dd><a href="#listed" title=category-listed-form-element>Listed form
- element</a>.
+ <dd><a href="#listed" title=category-listed>Listed</a> and <a
+ href="#resettable" title=category-reset>resettable</a> <a
+ href="#form-associated">form-associated element</a>.
<dt>Contexts in which this element may be used:
@@ -27401,21 +27418,21 @@
<p>When a <a href="#form-associated">form-associated element</a>'s ancestor
chain changes, e.g. because it or one of its ancestors was inserted or
removed from a <code>Document</code>, then the user agent must <a
- href="#reset">reset the form owner</a> of that element.
+ href="#reset0">reset the form owner</a> of that element.
<p>When a <a href="#form-associated">form-associated element</a>'s <code
title=attr-fae-form><a href="#form0">form</a></code> attribute is added,
removed, or has its value changed, then the user agent must <a
- href="#reset">reset the form owner</a> of that element.
+ href="#reset0">reset the form owner</a> of that element.
<p>When a <a href="#form-associated">form-associated element</a> has a
<code title=attr-fae-form><a href="#form0">form</a></code> attribute and
the ID of any of the <code><a href="#form">form</a></code> elements in the
<code>Document</code> changes, then the user agent must <a
- href="#reset">reset the form owner</a> of that <a
+ href="#reset0">reset the form owner</a> of that <a
href="#form-associated">form-associated element</a>.
- <p>When the user agent is to <dfn id=reset>reset the form owner</dfn> of a
+ <p>When the user agent is to <dfn id=reset0>reset the form owner</dfn> of a
<a href="#form-associated">form-associated element</a>, it must run the
following steps:
@@ -27575,10 +27592,10 @@
is to perform the submission).
<li>
- <p>Let <var title="">controls</var> be a list of all the <a href="#field"
- title=category-field>field elements</a> whose <a href="#form-owner">form
- owner</a> is <var title="">form</var>, in <a href="#tree-order">tree
- order</a>.
+ <p>Let <var title="">controls</var> be a list of all the <a
+ href="#submittable" title=category-submit>submittable</a> elements whose
+ <a href="#form-owner">form owner</a> is <var title="">form</var>, in <a
+ href="#tree-order">tree order</a>.
<li>
<p>Let the <var title="">form data set</var> be a list of name/value
@@ -28148,6 +28165,25 @@
encoding. -->
</ol>
+ <h4 id=resetting><span class=secno>4.9.17 </span>Resetting a form</h4>
+
+ <p>When a form <var title="">form</var> is <dfn id=reset1
+ title=concept-form-reset>reset</dfn>, the user agent must invoke the <a
+ href="#reset2" title=concept-form-reset-control>reset algorithm</a> of
+ each <a href="#resettable" title=category-reset>resettable</a> elements
+ whose <a href="#form-owner">form owner</a> is <var title="">form</var>,
+ and must then <a href="#dispatch">dispatch a <code
+ title=event-formchange>formchange</code> event</a>.
+
+ <p>Each <a href="#resettable" title=category-reset>resettable</a> element
+ defines its own <dfn id=reset2 title=concept-form-reset-control>reset
+ algorithm</dfn>.
+
+ <h4 id=event><span class=secno>4.9.18 </span>Event dispatch</h4>
+
+ <p class=big-issue>When the user agent is to <dfn id=dispatch>dispatch a
+ <code title=event-formchange>formchange</code> event</dfn>, ...
+
<h3 id=scripting1><span class=secno>4.10 </span>Scripting</h3>
<p>Scripts allow authors to add interactivity to their documents.
@@ -33975,7 +34011,7 @@
void <a href="#postmessage0" title=dom-window-postMessage-2>postMessage</a>(in DOMString message, in DOMString targetOrigin);
void <a href="#postmessage1" title=dom-window-postMessage-3>postMessage</a>(in DOMString message, in <a href="#messageport0">MessagePort</a> messagePort, in DOMString targetOrigin);
- // <a href="#event6">event handler DOM attributes</a>
+ // <a href="#event7">event handler DOM attributes</a>
attribute <span>EventListener</span> <a href="#onabort" title=handler-onabort>onabort</a>;
attribute <span>EventListener</span> <a href="#onbeforeunload" title=handler-onbeforeunload>onbeforeunload</a>;
attribute <span>EventListener</span> <a href="#onblur" title=handler-onblur>onblur</a>;
@@ -34264,7 +34300,7 @@
<dd>The owner is the <code>Document</code> to which the <code><a
href="#script1">script</a></code> element belongs.
- <dt>If a script is in an <a href="#event5" title="event handler content
+ <dt>If a script is in an <a href="#event6" title="event handler content
attributes">event handler content attribute</a>
<dd>The owner is the <code>Document</code> to which the attribute node
@@ -34609,8 +34645,8 @@
rule in a CSS <code><a href="#style1">style</a></code> element block).
<li>Event handlers, whether registered through the DOM using <code
- title="">addEventListener()</code>, by explicit <a href="#event5">event
- handler content attributes</a>, by <a href="#event6">event handler DOM
+ title="">addEventListener()</code>, by explicit <a href="#event6">event
+ handler content attributes</a>, by <a href="#event7">event handler DOM
attributes</a>, or otherwise.
<li>Processing of technologies like XBL or SVG that have their own
@@ -34700,24 +34736,24 @@
will disable any event handler attributes, event listeners, timeouts, etc,
that were set by scripts in the document.
- <h4 id=event><span class=secno>5.4.2 </span>Event loops</h4>
+ <h4 id=event0><span class=secno>5.4.2 </span>Event loops</h4>
<p>To coordinate events, user interaction, scripts, rendering, networking,
- and so forth, user agents must use <dfn id=event3 title="event loop">event
+ and so forth, user agents must use <dfn id=event4 title="event loop">event
loops</dfn> as described in this section.
- <p>There must be at least one <a href="#event3">event loop</a> per user
- agent, and at most one <a href="#event3">event loop</a> per <a
+ <p>There must be at least one <a href="#event4">event loop</a> per user
+ agent, and at most one <a href="#event4">event loop</a> per <a
href="#unit-of0">unit of related similar-origin browsing contexts</a>.
- <p>An <a href="#event3">event loop</a> always has at least one <a
- href="#browsing1">browsing context</a>. If an <a href="#event3">event
+ <p>An <a href="#event4">event loop</a> always has at least one <a
+ href="#browsing1">browsing context</a>. If an <a href="#event4">event
loop</a>'s <a href="#browsing1" title="browsing context">browsing
- contexts</a> all go away, then the <a href="#event3">event loop</a> goes
+ contexts</a> all go away, then the <a href="#event4">event loop</a> goes
away as well. A <a href="#browsing1">browsing context</a> always has an <a
- href="#event3">event loop</a> coordinating its activities.
+ href="#event4">event loop</a> coordinating its activities.
- <p>An <a href="#event3">event loop</a> has one or more <dfn id=task-queues
+ <p>An <a href="#event4">event loop</a> has one or more <dfn id=task-queues
title="task queue">task queues</dfn>. A <a href="#task-queues">task
queue</a> is an ordered list of <dfn id=tasks
title=concept-task>tasks</dfn>, which can be:
@@ -34760,7 +34796,7 @@
<p>When a user agent is to <dfn id=queue>queue a task</dfn>, it must add
the given task to one of the <a href="#task-queues" title="task
- queue">task queues</a> of the relevant <a href="#event3">event loop</a>.
+ queue">task queues</a> of the relevant <a href="#event4">event loop</a>.
All the tasks from one particular <dfn id=task-source>task source</dfn>
(e.g. the callbacks generated by timers, the events dispatched for mouse
movements, the tasks queued for the parser) must always be added to the
@@ -34777,12 +34813,12 @@
starving other task queues, and never processing events from any one <a
href="#task-source">task source</a> out of order.
- <p>An <a href="#event3">event loop</a> must continually run through the
+ <p>An <a href="#event4">event loop</a> must continually run through the
following steps for as long as it exists:
<ol>
<li>
- <p>Run the oldest task on one of the <a href="#event3">event loop</a>'s
+ <p>Run the oldest task on one of the <a href="#event4">event loop</a>'s
<a href="#task-queues" title="task queue">task queues</a>. The user
agent may pick any <a href="#task-queues">task queue</a>.
@@ -34795,7 +34831,7 @@
reflect the current state.
<li>
- <p>Return to the first step of the <a href="#event3">event loop</a>.
+ <p>Return to the first step of the <a href="#event4">event loop</a>.
</ol>
<h4 id=security4><span class=secno>5.4.3 </span>Security exceptions</h4>
@@ -34904,13 +34940,13 @@
handler attributes</h5>
<!-- 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 -->
- <p><a href="#html-elements">HTML elements</a> can have <dfn id=event4>event
+ <p><a href="#html-elements">HTML elements</a> can have <dfn id=event5>event
handler attributes</dfn> specified. These act as bubbling event listeners
for the element on which they are specified.
- <p>Each event handler attribute has two parts, an <a href="#event5"
+ <p>Each event handler attribute has two parts, an <a href="#event6"
title="event handler content attributes">event handler content
- attribute</a> and an <a href="#event6" title="event handler DOM
+ attribute</a> and an <a href="#event7" title="event handler DOM
attributes">event handler DOM attribute</a>. Event handler attributes must
initially be set to null. When their value changes (through the changing
of their event handler content attribute or their event handler DOM
@@ -34918,11 +34954,11 @@
<code>EventListener</code> object assigned to them.
<p>Objects other than <code>Element</code> objects, in particular <code><a
- href="#window">Window</a></code>, only have <a href="#event6" title="event
+ href="#window">Window</a></code>, only have <a href="#event7" title="event
handler DOM attributes">event handler DOM attribute</a> (since they have
no content attributes).
- <p><dfn id=event5>Event handler content attributes</dfn>, when specified,
+ <p><dfn id=event6>Event handler content attributes</dfn>, when specified,
must contain valid ECMAScript code matching the ECMAScript <code
title="">FunctionBody</code> production. <a
href="#references">[ECMA262]</a></p>
@@ -34965,7 +35001,7 @@
<p class=big-issue>How do we allow non-JS event handlers?
- <p><dfn id=event6>Event handler DOM attributes</dfn>, on setting, must set
+ <p><dfn id=event7>Event handler DOM attributes</dfn>, on setting, must set
the corresponding event handler attribute to their new value, and on
getting, must return whatever the current value of the corresponding event
handler attribute is (possibly null).
@@ -35321,7 +35357,7 @@
otherwise. (The <var title=dom-event-listener>listener</var> argument is
emphatically <em>not</em> the event handler attribute itself.)
- <h5 id=event0><span class=secno>5.4.5.2. </span>Event firing</h5>
+ <h5 id=event1><span class=secno>5.4.5.2. </span>Event firing</h5>
<p class=big-issue>maybe this should be moved higher up (terminology?
conformance? DOM?) Also, the whole terminology thing should be changed so
@@ -37732,7 +37768,7 @@
cache</var>.
</ol>
- <p>The following are the <a href="#event6">event handler DOM attributes</a>
+ <p>The following are the <a href="#event7">event handler DOM attributes</a>
that must be supported by objects implementing the <code><a
href="#applicationcache">ApplicationCache</a></code> interface:
@@ -39513,7 +39549,7 @@
the two documents are in the same <a href="#unit-of">unit of related
browsing contexts</a>, or null otherwise.
- <h6 id=event1><span class=secno>5.10.1.5.1. </span>Event definition</h6>
+ <h6 id=event2><span class=secno>5.10.1.5.1. </span>Event definition</h6>
<pre class=idl>interface <dfn id=storageevent>StorageEvent</dfn> : Event {
readonly attribute DOMString <a href="#key" title=dom-StorageEvent-key>key</a>;
@@ -39564,11 +39600,11 @@
executing, other than in a way that is predictable by the script itself.
<p class=note>There are various ways of implementing this requirement. One
- is to just have one <a href="#event3">event loop</a> for all <a
+ is to just have one <a href="#event4">event loop</a> for all <a
href="#browsing1" title="browsing context">browsing contexts</a>. Another
is that if a script running in one browsing context accesses a storage
area, the user agent blocks scripts in other browsing contexts when they
- try to access the same storage area until the <a href="#event3">event
+ try to access the same storage area until the <a href="#event4">event
loop</a> running the first script has completed running the task that
started that script. Another (potentially more efficient but certainly
more complex) implementation strategy is to use optimistic transactional
@@ -44753,7 +44789,7 @@
<h2 id=comms><span class=secno>7. </span>Communication</h2>
- <h3 id=event2><span class=secno>7.1 </span>Event definitions</h3>
+ <h3 id=event3><span class=secno>7.1 </span>Event definitions</h3>
<p>Messages in <a href="#server-sent">server-sent events</a>, <a
href="#web-sockets">Web sockets</a>, <a
@@ -45167,7 +45203,7 @@
<p>The field is ignored.
</dl>
- <p id=dispatchMessage>When the user agent is required to <dfn id=dispatch
+ <p id=dispatchMessage>When the user agent is required to <dfn id=dispatch0
title="">dispatch the event</dfn>, then the user agent must act as
follows:
@@ -45458,7 +45494,7 @@
<hr>
- <p>The following are the <a href="#event6">event handler DOM attributes</a>
+ <p>The following are the <a href="#event7">event handler DOM attributes</a>
that must be supported by objects implementing the <code><a
href="#websocket0">WebSocket</a></code> interface:
@@ -46750,7 +46786,7 @@
<p>When a port's <a href="#port-message">port message queue</a> is open,
contains an event, and its owner is <a href="#available" title="port owner
available">available</a>, the user agent must <a href="#queue">queue a
- task</a> in the <a href="#event3">event loop</a> to dispatch the first
+ task</a> in the <a href="#event4">event loop</a> to dispatch the first
event in the queue on the <code><a
href="#messageport0">MessagePort</a></code> object, and remove the event
from the queue. The <a href="#task-source">task source</a> for this <a
@@ -46804,7 +46840,7 @@
<hr>
- <p>The following are the <a href="#event6">event handler DOM attributes</a>
+ <p>The following are the <a href="#event7">event handler DOM attributes</a>
that must be supported by objects implementing the <code><a
href="#messageport0">MessagePort</a></code> interface:
@@ -48663,7 +48699,7 @@
<hr>
- <p>When the steps below require the UA to <dfn id=reset0>reset the
+ <p>When the steps below require the UA to <dfn id=reset3>reset the
insertion mode appropriately</dfn>, it means the UA must follow these
steps:
@@ -53509,7 +53545,7 @@
<p>Pop elements from this stack until a <code><a
href="#table">table</a></code> element has been popped from the stack.</p>
- <p><a href="#reset0">Reset the insertion mode appropriately</a>.</p>
+ <p><a href="#reset3">Reset the insertion mode appropriately</a>.</p>
<dt>An end tag whose tag name is one of: "body", "caption", "col",
"colgroup", "html", "tbody", "td", "tfoot", "th", "thead", "tr"
@@ -54113,7 +54149,7 @@
until a <code><a href="#select">select</a></code> element has been
popped from the stack.</p>
- <p><a href="#reset0">Reset the insertion mode appropriately</a>.</p>
+ <p><a href="#reset3">Reset the insertion mode appropriately</a>.</p>
<dt>A start tag whose tag name is "select"
@@ -55170,7 +55206,7 @@
that it contains just the single element <var title="">root</var>.</p>
<li>
- <p><a href="#reset0" title="reset the insertion mode appropriately">Reset
+ <p><a href="#reset3" title="reset the insertion mode appropriately">Reset
the parser's insertion mode appropriately</a>.</p>
<p class=note>The parser will reference the <var title="">context</var>
Received on Saturday, 13 September 2008 01:08:03 UTC