spec/Overview.html 1.1562 2390 WF2: forminput/formchange, rework how <o from poot on 2008-11-06 (public-html-diffs@w3.org from November 2008)

From: poot <cvsmail@w3.org>
Date: Fri, 7 Nov 2008 06:54:10 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20081106215410.B0B8E2BC74@toro.w3.mag.keio.ac.jp>
WF2: forminput/formchange, rework how <option> defines a command, and
editorial fixes. (whatwg r2390)

4.10.4.2 Common input element attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#common-input-element-attributes
Firing a click event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#fire-a-click-event
toggle
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#concept-select-toggle
4.10.4.1.19 Reset Button state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#reset-button-state
picked
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#concept-select-pick
4.10.4.1.14 Checkbox state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#checkbox-state
radio button group
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#radio-button-group
unfocusing steps
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#unfocusing-steps
selected coordinate
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#concept-input-type-image-coordinate
change
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#event-input-change
4.10.4.1.1 Hidden state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#hidden-state
size
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#attr-select-size
4.10.4.1.20 Button state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#button-state
4.11.6.4 Using the option element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#using-the-option-element-to-define-a-command
selectedOption
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#dom-input-selectedoption
4.10.5 The button element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#the-button-element
4.11 Interactive elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#interactive-elements
4.10.4.4 Common event behaviors
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#common-event-behaviors
Firing a contextmenu event
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#fire-a-contextmenu-event
4.10.4.1.17 Submit Button state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#submit-button-state
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#status-of-this-document
4.10.4.1.18 Image Button state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#image-button-state
4.11.6.5 Using the command element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#using-the-command-element-to-define-a-command
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
broadcast formchange events
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#broadcast-formchange-events
Editor's Draft 6 November 2008
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#editor-s-draft-date-zzz-9-june-2008
4.10.4.1.2 Text state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1562.html#text-state

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1561&r2=1.1562&f=h
http://html5.org/tools/web-apps-tracker?from=2389&to=2390

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1561
retrieving revision 1.1562
diff -u -d -r1.1561 -r1.1562
--- Overview.html 5 Nov 2008 16:35:01 -0000 1.1561
+++ Overview.html 6 Nov 2008 21:49:41 -0000 1.1562
@@ -8,7 +8,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->5 November 2008</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->6 November 2008</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2008/WD-html5-20080610/">http://www.w3.org/TR/2008/WD-html5-20080610/</a></dd>
@@ -97,7 +97,7 @@
   specification's progress along the W3C Recommendation
   track.
   <!--ZZZ:-->
-  This specification is the 5 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
+  This specification is the 6 November 2008 <!--ZZZ "Working Draft"-->Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -19823,7 +19823,7 @@
    <code class=no-backref title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code>, and
    <code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> methods.</p>
 
-   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not fire.</p>
+   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not apply.</p>
 
   </div><h6 id=text-state><span class=secno>4.10.4.1.2 </span><dfn title=attr-input-type-text>Text</dfn> state</h6><p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#text-state title=attr-input-type-text>Text</a> state, the rules in this
   section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a one line plain text
@@ -20777,7 +20777,8 @@
   value it had before the <a href=#pre-click-activation-steps>pre-click activation steps</a> were
   run. The <a href=#activation-behavior>activation behavior</a> is to <a href=#fire-a-simple-event>fire a simple
   event</a> called <code title=event-change>change</code> at the
-  element.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and its <a href=#concept-fe-checked title=concept-fe-checked>checkedness</a> is false, then the
+  element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+  element's <a href=#form-owner>form owner</a>.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and its <a href=#concept-fe-checked title=concept-fe-checked>checkedness</a> is false, then the
   element is <a href=#suffering-from-being-missing>suffering from being missing</a>.<div class=bookkeeping>
 
    <p>The following common <code><a href=#the-input-element>input</a></code> element content
@@ -20863,7 +20864,8 @@
   the element's <a href=#concept-fe-checked title=concept-fe-checked>checkedness</a> to
   false. The <a href=#activation-behavior>activation behavior</a> is to <a href=#fire-a-simple-event>fire a
   simple event</a> called <code title=event-change>change</code>
-  at the element.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and all of the
+  at the element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+  element's <a href=#form-owner>form owner</a>.<p><strong>Constraint validation:</strong> If the element is <i title=concept-input-required><a href=#concept-input-required>required</a></i> and all of the
   <code><a href=#the-input-element>input</a></code> elements in the <i><a href=#radio-button-group>radio button group</a></i> have a
   <a href=#concept-fe-checked title=concept-fe-checked>checkedness</a> that is
   false, then the element is <a href=#suffering-from-being-missing>suffering from being
@@ -21042,7 +21044,7 @@
    <code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> and
    <code class=no-backref title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code> methods.</p>
 
-   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not fire.</p>
+   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not apply.</p>
 
   </div><h6 id=image-button-state><span class=secno>4.10.4.1.18 </span><dfn title=attr-input-type-image>Image Button</dfn> state</h6><p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state, the rules
   in this section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents either an image from
@@ -21167,7 +21169,7 @@
    <code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> and
    <code class=no-backref title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code> methods.</p>
 
-   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not fire.</p>
+   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not apply.</p>
 
   </div><p class=note>Many aspects of this state's behavior are similar to
   the behavior of the <code><a href=#the-img-element>img</a></code> element. Readers are encouraged
@@ -21214,7 +21216,7 @@
    <code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> and
    <code class=no-backref title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code> methods.</p>
 
-   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not fire.</p>
+   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not apply.</p>
 
   </div><h6 id=button-state><span class=secno>4.10.4.1.20 </span><dfn title=attr-input-type-button>Button</dfn> state</h6><p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#button-state title=attr-input-type-button>Button</a> state, the rules in
   this section apply.<p>The <code><a href=#the-input-element>input</a></code> element represents a button with no
@@ -21256,7 +21258,7 @@
    <code class=no-backref title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> and
    <code class=no-backref title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code> methods.</p>
 
-   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not fire.</p>
+   <p>The <code class=no-backref title=event-input-input><a href=#event-input-input>input</a></code> and <code class=no-backref title=event-input-change><a href=#event-input-change>change</a></code> events do not apply.</p>
 
   </div><h5 id=common-input-element-attributes><span class=secno>4.10.4.2 </span>Common <code><a href=#the-input-element>input</a></code> element attributes</h5><p>These attributes only apply to an <code><a href=#the-input-element>input</a></code> element if
   its <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in a
@@ -21594,8 +21596,10 @@
   it contains no matching <code><a href=#the-option-element>option</a></code> element, then the <code title=dom-input-selectedOption><a href=#dom-input-selectedoption>selectedOption</a></code> attribute
   must return null.<h5 id=common-event-behaviors><span class=secno>4.10.4.4 </span>Common event behaviors</h5><p>When the <dfn id=event-input-input title=event-input-input><code>input</code></dfn>
   event applies, the user agent must <a href=#queue-a-task>queue a task</a> to
-  <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code> element
-  any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change. User agents may
+  <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code> element,
+  then <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code>
+  events</a> at the <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form
+  owner</a>, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change. User agents may
   wait for a suitable break in the user's interaction before queuing
   the task; for example, a user agent could wait for the user to have
   not hit a key for 100ms, so as to only fire the event when the user
@@ -21603,8 +21607,10 @@
   if the element does not have an <a href=#activation-behavior>activation behavior</a>
   defined but uses a user interface that involves an explicit commit
   action, then the user agent must <a href=#queue-a-task>queue a task</a> to
-  <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code> element
-  any time the user commits a change to the element's <a href=#concept-fe-value title=concept-fe-value>value</a> or list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>.<p class=example>An example of a user interface with a commit
+  <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
+  element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+  <code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>, any time the
+  user commits a change to the element's <a href=#concept-fe-value title=concept-fe-value>value</a> or list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>.<p class=example>An example of a user interface with a commit
   action would be a <a href=#file-upload-state title=attr-input-type-file>File
   Upload</a> control that consists of a single button that brings
   up a file selection dialog: when the dialog is closed, if that the
@@ -21615,7 +21621,7 @@
   from a drop-down calendar: while text input might not have an
   explicit commit step, selecting a date from the drop down calendar
   and then dismissing the drop down would be a commit action.<p class=note>In addition, when the <code title=event-input-change><a href=#event-input-change>change</a></code> event applies, <code title=event-change>change</code> events can also be fired as part
-  of the element's <span>action behavior</span> and as part of the
+  of the element's <a href=#activation-behavior>activation behavior</a> and as part of the
   <a href=#unfocusing-steps>unfocusing steps</a>.<p>The <a href=#task-source>task source</a> for these <span title=concept-tasks>task</span> is the <a href=#user-interaction-task-source>user interaction task
   source</a>.<h4 id=the-button-element><span class=secno>4.10.5 </span>The <dfn><code>button</code></dfn> element</h4><dl class=element><dt>Categories</dt>
    <dd><a href=#phrasing-content-0>Phrasing content</a>.</dd>
@@ -21799,15 +21805,17 @@
   should allow the user to pick an <code><a href=#the-option-element>option</a></code> element in its
   <a href=#concept-select-option-list title=concept-select-option-list>list of options</a> that
   is itself not <a href=#concept-option-disabled title=concept-option-disabled>disabled</a>. Upon this
-  <code><a href=#the-option-element>option</a></code> element being picked (either through a click, or
+  <code><a href=#the-option-element>option</a></code> element being <dfn id=concept-select-pick title=concept-select-pick>picked</dfn> (either through a click, or
   through unfocusing the element after changing its value, or through
-  any other mechanism), and before the relevant user interaction event
-  is queued (e.g. before the <span title=event-click>click</span>
+  a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or through any
+  other mechanism), and before the relevant user interaction event is
+  queued (e.g. before the <span title=event-click>click</span>
   event), the user agent must set the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
   picked <code><a href=#the-option-element>option</a></code> element to true and then <a href=#queue-a-task>queue a
   task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the <code><a href=#the-select-element>select</a></code>
   element, using the <a href=#user-interaction-task-source>user interaction task source</a> as the
-  task source.<p>If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code>
+  task source, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+  element's <a href=#form-owner>form owner</a>.<p>If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code>
   attribute is absent, whenever an <code><a href=#the-option-element>option</a></code> element in the
   <code><a href=#the-select-element>select</a></code> element's <a href=#concept-select-option-list title=concept-select-option-list>list of options</a> has its
   <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> set to
@@ -21824,16 +21832,19 @@
   <a href=#tree-order>tree order</a> that is not <a href=#concept-option-disabled title=concept-option-disabled>disabled</a>, if any, to
   true.<p>If the <code title=attr-select-multiple><a href=#attr-select-multiple>multiple</a></code>
   attribute is present, and the element is not <a href=#concept-fe-disabled title=concept-fe-disabled>disabled</a>, then the user agent
-  should allow the user to toggle the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
+  should allow the user to <dfn id=concept-select-toggle title=concept-select-toggle>toggle</dfn> the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
   <code><a href=#the-option-element>option</a></code> elements in its <a href=#concept-select-option-list title=concept-select-option-list>list of options</a> that are
-  themselves not <a href=#concept-option-disabled title=concept-option-disabled>disabled</a>. Upon the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of one or
+  themselves not <a href=#concept-option-disabled title=concept-option-disabled>disabled</a>
+  (either through a click, or through a <a href=#using-the-option-element-to-define-a-command title=option-command>menu command</a>, or any other
+  mechanism). Upon the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of one or
   more <code><a href=#the-option-element>option</a></code> elements being changed by the user, and
   before the relevant user interaction event is queued (e.g. before a
   related <span title=event-click>click</span> event), the user
   agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
   event</a> called <code title=event-change>change</code> at the
   <code><a href=#the-select-element>select</a></code> element, using the <a href=#user-interaction-task-source>user interaction task
-  source</a> as the task source.<p>The <a href=#concept-form-reset-control title=concept-form-reset-control>reset
+  source</a> as the task source, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
+  element's <a href=#form-owner>form owner</a>.<p>The <a href=#concept-form-reset-control title=concept-form-reset-control>reset
   algorithm</a> for <code><a href=#the-select-element>select</a></code> elements is to go through
   all the <code><a href=#the-option-element>option</a></code> elements in the element's <a href=#concept-select-option-list title=concept-select-option-list>list of options</a>, and set
   their <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a>
@@ -23319,8 +23330,7 @@
    <a href=#tree-order>tree order</a>, <a href=#fire-a-simple-event>fire a simple event</a> named
    <var title="">event name</var> at the element.</li>
 
-  </ol><p class=XXX>Still need to define when formchange and forminput
-  fire naturally.<h3 id=interactive-elements><span class=secno>4.11 </span>Interactive elements</h3><h4 id=the-details-element><span class=secno>4.11.1 </span>The <dfn><code>details</code></dfn> element</h4><dl class=element><dt>Categories</dt>
+  </ol><h3 id=interactive-elements><span class=secno>4.11 </span>Interactive elements</h3><h4 id=the-details-element><span class=secno>4.11.1 </span>The <dfn><code>details</code></dfn> element</h4><dl class=element><dt>Categories</dt>
    <dd><a href=#flow-content-0>Flow content</a>.</dd>
    <dd><a href=#interactive-content-0>Interactive content</a>.</dd>
    <dt>Contexts in which this element may be used:</dt>
@@ -25452,26 +25462,21 @@
   command is an <a href=#anonymous-command>anonymous command</a>.<p>The <a href=#command-facet-label title=command-facet-Label>Label</a> of the command
   is the value of the <code><a href=#the-option-element>option</a></code> element's <code title=attr-option-label><a href=#attr-option-label>label</a></code> attribute, if there is one,
   or the value of the <code><a href=#the-option-element>option</a></code> element's
-  <code><a href=#textcontent>textContent</a></code> DOM attribute if it doesn't.<p>The <a href=#command-facet-hint title=command-facet-Hint>Hint</a> of the command
+  <code><a href=#textcontent>textContent</a></code> DOM attribute if there isn't.<p>The <a href=#command-facet-hint title=command-facet-Hint>Hint</a> of the command
   is the string given by the element's <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute, if any, and the empty
   string if the attribute is absent.<p>There is no <a href=#command-facet-icon title=command-facet-Icon>Icon</a> for the
   command.<p>The <a href=#command-facet-hiddenstate title=command-facet-HiddenState>Hidden State</a>
   of the command is true (hidden) if the element has a <code title=attr-hidden><a href=#the-hidden-attribute>hidden</a></code> attribute, and false
   otherwise.<p>The <a href=#command-facet-disabledstate title=command-facet-DisabledState>Disabled
-  State</a> of the command is true (disabled) if the element has a
-  <code title=attr-option-disabled><a href=#attr-option-disabled>disabled</a></code> attribute, and
-  false otherwise.<p>The <a href=#command-facet-checkedstate title=command-facet-CheckedState>Checked State</a>
-  of the command is true (checked) if the element's <code title=dom-option-selected><a href=#dom-option-selected>selected</a></code> DOM attribute is true,
-  and false otherwise.<p>The <a href=#command-facet-action title=command-facet-Action>Action</a> of the
-  command depends on its <a href=#command-facet-type title=command-facet-Type>Type</a>. If the command is of <a href=#command-facet-type title=command-facet-Type>Type</a> "radio" then this must set
-  the <code title=dom-option-selected><a href=#dom-option-selected>selected</a></code> DOM attribute
-  of the <code><a href=#the-option-element>option</a></code> element to true, otherwise it must toggle
-  the state of the <code title=dom-option-selected><a href=#dom-option-selected>selected</a></code>
-  DOM attribute (set it to true if it is false and vice versa). Then
-  <a href=#fire-a-change-event title="fire a change event">a <code title="">change</code>
-  event must be fired</a> on the <code><a href=#the-option-element>option</a></code> element's
-  nearest ancestor <code><a href=#the-select-element>select</a></code> element (if there is one), as
-  if the selection had been changed directly.<h5 id=using-the-command-element-to-define-a-command><span class=secno>4.11.6.5 </span>Using the <dfn title=command-element><code>command</code></dfn> element to define
+  State</a> of the command is true (disabled) if the element is
+  <a href=#concept-option-disabled title=concept-option-disabled>disabled</a> or if its
+  nearest ancestor <code><a href=#the-select-element>select</a></code> element is <a href=#concept-option-disabled title=concept-option-disabled>disabled</a>, and false
+  otherwise.<p>The <a href=#command-facet-checkedstate title=command-facet-CheckedState>Checked State</a>
+  of the command is true (checked) if the element's <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> is true, and
+  false otherwise.<p>The <a href=#command-facet-action title=command-facet-Action>Action</a> of the
+  command depends on its <a href=#command-facet-type title=command-facet-Type>Type</a>. If the command is of <a href=#command-facet-type title=command-facet-Type>Type</a> "radio" then it must <a href=#concept-select-pick title=concept-select-pick>pick</a> the <code><a href=#the-option-element>option</a></code>
+  element. Otherwise, it must <a href=#concept-select-toggle title=concept-select-toggle>toggle</a> the <code><a href=#the-option-element>option</a></code>
+  element.<h5 id=using-the-command-element-to-define-a-command><span class=secno>4.11.6.5 </span>Using the <dfn title=command-element><code>command</code></dfn> element to define
   a command</h5><p>A <code><a href=#the-command>command</a></code> element <a href=#concept-command title=concept-command>defines a command</a>.<p>The <a href=#command-facet-type title=command-facet-Type>Type</a> of the command
   is "radio" if the <code><a href=#the-command>command</a></code>'s <code title=attr-command-type><a href=#attr-command-type>type</a></code> attribute is
   "<code>radio</code>", "checkbox" if the attribute's value is
@@ -26950,10 +26955,7 @@
   set according to the current state of the key input device, if any
   (false for any keys that are not available), its <code title="">detail</code> attribute set to 1, and its <code title="">relatedTarget</code> attribute set to null. The <code title="">getModifierState()</code> method on the object must return
   values appropriately describing the state of the key input device at
-  the time the event is created.<p><dfn id=fire-a-change-event title="fire a change event">Firing a <code title=event-change>change</code> event</dfn> means that a <a href=http://www.w3.org/TR/DOM-Level-3-Events/events.html#event-change><code>change</code></a>
-  event with no namespace, which bubbles but is not cancelable, and
-  which uses the <code>Event</code> interface, must be dispatched at
-  the given element.<p><dfn id=fire-a-contextmenu-event title="fire a contextmenu event">Firing a <code title=event-contextmenu>contextmenu</code> event</dfn> means that
+  the time the event is created.<p><dfn id=fire-a-contextmenu-event title="fire a contextmenu event">Firing a <code title=event-contextmenu>contextmenu</code> event</dfn> means that
   a <code title=event-contextmenu>contextmenu</code> event with no
   namespace, which bubbles and is cancelable, and which uses the
   <code>Event</code> interface, must be dispatched at the given
@@ -31707,7 +31709,9 @@
    element, and the element does not have a defined <a href=#activation-behavior>activation
    behavior</a>, and the user has changed the element's <a href=#concept-fe-value title=concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>
    while the control was focused without committing that change, then
-   <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the element.</p>
+   <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-change>change</code> at the element, then
+   <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code>
+   events</a> at the element's <a href=#form-owner>form owner</a>.</p>
 
    <li><p>Unfocus the element.</li>
Received on Thursday, 6 November 2008 21:55:19 UTC