- From: poot <cvsmail@w3.org>
- Date: Thu, 18 Sep 2008 09:46:02 +0900 (JST)
- To: public-html-diffs@w3.org
WF2: Define input.valueAsDate and input.valueAsNumber for the cases
where they don't apply. (whatwg r2212)
input
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#input0
high
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#high0
4.11.2.4.1. Common default data provider method definitions for cells
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#commonDefaultDataGridMethodDefinitions
meter
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#meter
list
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#list
checked
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#checked1
valueAsNumber
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasnumber
valueAsDate getter algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasdate0
HTMLParamElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmlparamelement
low
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#low0
strip line breaks from the value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#strip
optimum
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#optimum
HTMLMeterElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmlmeterelement
HTMLInputElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmlinputelement
4.9.14 Attributes for form submission
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#attributes2
4.11.6.3. Using the input element to define a command
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#using1
HTMLOptionElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmloptionelement
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value11
min
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#min
optimum
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#optimum0
start
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#start0
4.9.4.3. Common input element APIs
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#common5
4.9.4.1.21. Common algorithms
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#common3
param
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#param
li
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#li
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value7
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value6
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value5
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value4
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value3
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value2
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value1
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value0
progress
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#progress
parameter
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#parameter
valueAsNumber getter algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasnumber0
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value9
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value8
valueAsNumber setter algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasnumber1
HTMLLIElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmllielement
valueAsDate setter algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasdate1
max
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#max
defaultValue
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#defaultvalue
default value change algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#default2
4.9.4.3.2. Others...
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#others...
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#name6
name
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#name5
Constructing the form data set. For each element field in controls, in tree order, run the following substeps: If any of the following conditions are met, then skip these substeps for this element: The field element has a datalist element ancestor. The field element is disabled. The field element is a button but it is not submitter. The field element is an input element whose type attribute is in the Checkbox state and the control is not checked. The field element is an input element whose type attribute is in the Radio Button state and the control is not checked. The field element is an input element whose type attribute is in the File Upload state but the control does not have any files selected. Otherwise, process field as follows: If the field element is an input element whose type attribute is in the Image Button state, then run these further nested substeps: If the field element has an name attribute specified and value is not the empty string, let name be that value followed by a single U+002E FULL SOP (.) character. Otherwise, let name be the empty string. Let namex be the string consisting of the concatenation of name and a single U+0078 LATIN SMALL LETTER X (x) character. Let namey be the string consisting of the concatenation of name and a single U+0079 LATIN SMALL LETTER Y (y) character. The field element is submitter, and before this algorithm was invoked the user indicated a coordinate. Let x be the x-component of the coordindate selected by the user, and let y be the y-component of the coordinate selected by the user. Append an entry in the form data set with the name namex and the value x. Append an entry in the form data set with the name namey and the value y. Skip the remaining substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. If the field element does not have a name attribute specified, or its name attribute's value is the empty strig, skip these substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. Let name be the value of the field element's name attribute. If the field element is a select element, then for each option element in the select element that is selected, append an entry in the form data set with the name as the name and the value of the option element as the value. Otherwise, if the field element is an input element whose type attribute is in the File Upload state, then for each file selected in the input element, append an entry in the form data set with the name as the name and the file as the value. (Both the file name and the file contents are subsequently used.) Otherwise, append an entry in the form data set with name as the name and the value of the field element as the value.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#constructing-form-data-set
value
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value10
min
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#min0
HTMLProgressElement
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#htmlprogresselement
Insert, and wrap text in, semantic elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#contenteditable-wrapSemantic
dirty
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#dirty0
selected
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#selected1
max
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#max2
max
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#max0
max
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#max1
valueAsDate
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#valueasdate
control initialization algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#control0
4.9.4.3.1. Value manipulation
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#value
p
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#p
Attribute values
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#attribute4
Option()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#option0
disabled
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#disabled6
4.9.4.1.1. Text state
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#text-state
4.9.4.2. Common input element attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1385.html#common4
http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1384&r2=1.1385&f=h
http://html5.org/tools/web-apps-tracker?from=2211&to=2212
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1384
retrieving revision 1.1385
diff -u -d -r1.1384 -r1.1385
--- Overview.html 18 Sep 2008 00:21:31 -0000 1.1384
+++ Overview.html 18 Sep 2008 00:42:11 -0000 1.1385
@@ -1120,6 +1120,13 @@
<li><a href="#common5"><span class=secno>4.9.4.3. </span>Common
<code>input</code> element APIs</a>
+ <ul class=toc>
+ <li><a href="#value"><span class=secno>4.9.4.3.1. </span>Value
+ manipulation</a>
+
+ <li><a href="#others..."><span class=secno>4.9.4.3.2.
+ </span>Others...</a>
+ </ul>
</ul>
<li><a href="#the-button"><span class=secno>4.9.5 </span>The
@@ -12668,12 +12675,12 @@
href="#ol">ol</a></code> element's <code title=attr-ol-start><a
href="#start0">start</a></code> attribute, unless that <code><a
href="#li">li</a></code> element has a <code title=attr-li-value><a
- href="#value">value</a></code> attribute with a value that can be
+ href="#value0">value</a></code> attribute with a value that can be
successfully parsed, in which case it has the ordinal value given by that
- <code title=attr-li-value><a href="#value">value</a></code> attribute.
+ <code title=attr-li-value><a href="#value0">value</a></code> attribute.
<p>Each subsequent item in the list has the ordinal value given by its
- <code title=attr-li-value><a href="#value">value</a></code> attribute, if
+ <code title=attr-li-value><a href="#value0">value</a></code> attribute, if
it has one, or, if it doesn't, the ordinal value of the previous item,
plus one if the <code title=attr-ol-reversed><a
href="#reversed">reversed</a></code> is absent, or minus one if it is
@@ -12814,7 +12821,7 @@
<dt>Element-specific attributes:
<dd>If the element is a child of an <code><a href="#ol">ol</a></code>
- element: <code title=attr-li-value><a href="#value">value</a></code>
+ element: <code title=attr-li-value><a href="#value0">value</a></code>
<dd>If the element is not the child of an <code><a
href="#ol">ol</a></code> element: None.
@@ -12824,7 +12831,7 @@
<dd>
<pre
class=idl>interface <dfn id=htmllielement>HTMLLIElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
- attribute long <a href="#value0" title=dom-li-value>value</a>;
+ attribute long <a href="#value1" title=dom-li-value>value</a>;
};</pre>
</dl>
@@ -12836,25 +12843,25 @@
list-related relationship to any other <code><a href="#li">li</a></code>
element.
- <p>The <dfn id=value title=attr-li-value><code>value</code></dfn>
+ <p>The <dfn id=value0 title=attr-li-value><code>value</code></dfn>
attribute, if present, must be a <a href="#valid0">valid integer</a>
giving the ordinal value of the list item.
- <p>If the <code title=attr-li-value><a href="#value">value</a></code>
+ <p>If the <code title=attr-li-value><a href="#value0">value</a></code>
attribute is present, user agents must <a href="#rules0" title="rules for
parsing integers">parse it as an integer</a>, in order to determine the
attribute's value. If the attribute's value cannot be converted to a
number, the attribute must be treated as if it was absent. The attribute
has no default value.
- <p>The <code title=attr-li-value><a href="#value">value</a></code>
+ <p>The <code title=attr-li-value><a href="#value0">value</a></code>
attribute is processed relative to the element's parent <code><a
href="#ol">ol</a></code> element (q.v.), if there is one. If there is not,
the attribute has no effect.
- <p>The <dfn id=value0 title=dom-li-value><code>value</code></dfn> DOM
+ <p>The <dfn id=value1 title=dom-li-value><code>value</code></dfn> DOM
attribute must <a href="#reflect">reflect</a> the value of the <code
- title=dom-li-value><a href="#value0">value</a></code> content attribute.
+ title=dom-li-value><a href="#value1">value</a></code> content attribute.
<div class=example>
<p>The following example, the top ten movies are listed (in reverse
@@ -14272,7 +14279,7 @@
<dt>Element-specific attributes:
- <dd><code title=attr-progress-value><a href="#value1">value</a></code>
+ <dd><code title=attr-progress-value><a href="#value2">value</a></code>
<dd><code title=attr-progress-max><a href="#max">max</a></code>
@@ -14281,7 +14288,7 @@
<dd>
<pre
class=idl>interface <dfn id=htmlprogresselement>HTMLProgressElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
- attribute float <a href="#value2" title=dom-progress-value>value</a>;
+ attribute float <a href="#value3" title=dom-progress-value>value</a>;
attribute float <a href="#max0" title=dom-progress-max>max</a>;
readonly attribute float <a href="#position" title=dom-progress-position>position</a>;
};</pre>
@@ -14298,7 +14305,7 @@
<p>There are two attributes that determine the current task completion
represented by the element.
- <p>The <dfn id=value1 title=attr-progress-value><code>value</code></dfn>
+ <p>The <dfn id=value2 title=attr-progress-value><code>value</code></dfn>
attribute specifies how much of the task has been completed, and the <dfn
id=max title=attr-progress-max><code>max</code></dfn> attribute specifies
how much work the task requires in total. The units are arbitrary and not
@@ -14329,12 +14336,12 @@
<p><strong>Author requirements</strong>: The <code
title=attr-progress-max><a href="#max">max</a></code> and <code
- title=attr-progress-value><a href="#value1">value</a></code> attributes,
+ title=attr-progress-value><a href="#value2">value</a></code> attributes,
when present, must have values that are <a href="#valid1" title="valid
floating point number">valid floating point numbers</a>. The <code
title=attr-progress-max><a href="#max">max</a></code> attribute, if
present, must have a value greater than zero. The <code
- title=attr-progress-value><a href="#value1">value</a></code> attribute, if
+ title=attr-progress-value><a href="#value2">value</a></code> attribute, if
present, must have a value equal to or greater than zero, and less than or
equal to the value of the <code title=attr-progress-max><a
href="#max">max</a></code> attribute, if present.
@@ -14348,12 +14355,12 @@
<p><strong>User agent requirements</strong>: User agents must parse the
<code title=attr-progress-max><a href="#max">max</a></code> and <code
- title=attr-progress-value><a href="#value1">value</a></code> attributes'
+ title=attr-progress-value><a href="#value2">value</a></code> attributes'
values according to the <a href="#rules1">rules for parsing floating point
number values</a>.
<p>If the <code title=attr-progress-value><a
- href="#value1">value</a></code> attribute is omitted, then user agents
+ href="#value2">value</a></code> attribute is omitted, then user agents
must also parse the <code><a href="#textcontent">textContent</a></code> of
the <code><a href="#progress">progress</a></code> element in question
using the <a href="#steps">steps for finding one or two numbers of a ratio
@@ -14368,7 +14375,7 @@
<ol>
<li>If the <code title=attr-progress-max><a href="#max">max</a></code>
attribute is omitted, and the <code title=attr-progress-value><a
- href="#value1">value</a></code> is omitted, and the results of parsing
+ href="#value2">value</a></code> is omitted, and the results of parsing
the <code><a href="#textcontent">textContent</a></code> was nothing, then
the progress bar is an indeterminate progress bar. Abort these steps.
@@ -14380,7 +14387,7 @@
<li>Otherwise, if the <code title=attr-progress-max><a
href="#max">max</a></code> attribute is absent but the <code
- title=attr-progress-value><a href="#value1">value</a></code> attribute is
+ title=attr-progress-value><a href="#value2">value</a></code> attribute is
present, or, if the <code title=attr-progress-max><a
href="#max">max</a></code> attribute is present but no value could be
parsed from it, then the maximum is 1.
@@ -14395,19 +14402,19 @@
value is 1.
<li>If the <code title=attr-progress-value><a
- href="#value1">value</a></code> attribute is present on the element and a
+ href="#value2">value</a></code> attribute is present on the element and a
value could be parsed out of it, that value is the current value of the
progress bar. Otherwise, if the attribute is present but no value could
be parsed from it, the current value is zero.
<li>Otherwise if the <code title=attr-progress-value><a
- href="#value1">value</a></code> attribute is absent and the <code
+ href="#value2">value</a></code> attribute is absent and the <code
title=attr-progress-max><a href="#max">max</a></code> attribute is
present, then, if the <code><a href="#textcontent">textContent</a></code>
was parsed and found to contain just one number, with no associated
denominator punctuation character, then the current value is that number.
Otherwise, if the <code title=attr-progress-value><a
- href="#value1">value</a></code> attribute is absent and the <code
+ href="#value2">value</a></code> attribute is absent and the <code
title=attr-progress-max><a href="#max">max</a></code> attribute is
present then the current value is zero.
@@ -14431,14 +14438,14 @@
relative position of the current value relative to the maximum value.
<p>The <dfn id=max0 title=dom-progress-max><code>max</code></dfn> and <dfn
- id=value2 title=dom-progress-value><code>value</code></dfn> DOM attributes
+ id=value3 title=dom-progress-value><code>value</code></dfn> DOM attributes
must <a href="#reflect">reflect</a> the elements' content attributes of
the same name. When the relevant content attributes are absent, the DOM
attributes must return zero. The value parsed from the <code><a
href="#textcontent">textContent</a></code> never affects the DOM values.
<p class=big-issue>Would be cool to have the <code
- title=dom-progress-value><a href="#value2">value</a></code> DOM attribute
+ title=dom-progress-value><a href="#value3">value</a></code> DOM attribute
update the <code><a href="#textcontent">textContent</a></code> in-line...
<p>If the progress bar is an indeterminate progress bar, then the <dfn
@@ -14465,7 +14472,7 @@
<dt>Element-specific attributes:
- <dd><code title=attr-meter-value><a href="#value3">value</a></code>
+ <dd><code title=attr-meter-value><a href="#value4">value</a></code>
<dd><code title=attr-meter-min><a href="#min">min</a></code>
@@ -14482,7 +14489,7 @@
<dd>
<pre
class=idl>interface <dfn id=htmlmeterelement>HTMLMeterElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
- attribute float <a href="#value4" title=dom-meter-value>value</a>;
+ attribute float <a href="#value5" title=dom-meter-value>value</a>;
attribute float <a href="#min0" title=dom-meter-min>min</a>;
attribute float <a href="#max2" title=dom-meter-max>max</a>;
attribute float <a href="#low0" title=dom-meter-low>low</a>;
@@ -14514,7 +14521,7 @@
<p>The <dfn id=min title=attr-meter-min><code>min</code></dfn> attribute
specifies the lower bound of the range, and the <dfn id=max1
title=attr-meter-max><code>max</code></dfn> attribute specifies the upper
- bound. The <dfn id=value3 title=attr-meter-value><code>value</code></dfn>
+ bound. The <dfn id=value4 title=attr-meter-value><code>value</code></dfn>
attribute specifies the value to have the gauge indicate as the "measured"
value.
@@ -14538,7 +14545,7 @@
current value, and the minimum is assumed to be zero), or as a percentage
or similar (using one of the characters such as "%"), or as a fraction.
- <p>The <code title=attr-meter-value><a href="#value3">value</a></code>,
+ <p>The <code title=attr-meter-value><a href="#value4">value</a></code>,
<code title=attr-meter-min><a href="#min">min</a></code>, <code
title=attr-meter-low><a href="#low">low</a></code>, <code
title=attr-meter-high><a href="#high">high</a></code>, <code
@@ -14550,7 +14557,7 @@
<ul class=brief>
<li><code title=attr-meter-min><a href="#min">min</a></code> ≤ <code
- title=attr-meter-value><a href="#value3">value</a></code> ≤ <code
+ title=attr-meter-value><a href="#value4">value</a></code> ≤ <code
title=attr-meter-max><a href="#max1">max</a></code>
<li><code title=attr-meter-min><a href="#min">min</a></code> ≤ <code
@@ -14565,7 +14572,7 @@
<p>All <code><a href="#meter">meter</a></code> elements must have a value
specified somehow, either using the <code title=attr-meter-value><a
- href="#value3">value</a></code> attribute or by including a number in the
+ href="#value4">value</a></code> attribute or by including a number in the
contents of the element.
<p class=note>If no minimum or maximum is specified, then the range is
@@ -14620,14 +14627,14 @@
<p><strong>User agent requirements</strong>: User agents must parse the
<code title=attr-meter-min><a href="#min">min</a></code>, <code
title=attr-meter-max><a href="#max1">max</a></code>, <code
- title=attr-meter-value><a href="#value3">value</a></code>, <code
+ title=attr-meter-value><a href="#value4">value</a></code>, <code
title=attr-meter-low><a href="#low">low</a></code>, <code
title=attr-meter-high><a href="#high">high</a></code>, and <code
title=attr-meter-optimum><a href="#optimum">optimum</a></code> attributes
using the <a href="#rules1">rules for parsing floating point number
values</a>.
- <p>If the <code title=attr-meter-value><a href="#value3">value</a></code>
+ <p>If the <code title=attr-meter-value><a href="#value4">value</a></code>
attribute has been omitted, the user agent must also process the <code><a
href="#textcontent">textContent</a></code> of the element according to the
<a href="#steps">steps for finding one or two numbers of a ratio in a
@@ -14657,13 +14664,13 @@
href="#max1">max</a></code> attribute is specified but no value could be
parsed out of it, or if it was not specified, but either or both of the
<code title=attr-meter-min><a href="#min">min</a></code> or <code
- title=attr-meter-value><a href="#value3">value</a></code> attributes
+ title=attr-meter-value><a href="#value4">value</a></code> attributes
<em>were</em> specified, then the maximum value is 1.</p>
<p>Otherwise, none of the <code title=attr-meter-max><a
href="#max1">max</a></code>, <code title=attr-meter-min><a
href="#min">min</a></code>, and <code title=attr-meter-value><a
- href="#value3">value</a></code> attributes were specified. If the result
+ href="#value4">value</a></code> attributes were specified. If the result
of processing the <code><a href="#textcontent">textContent</a></code> of
the element was either nothing or just one number with no denominator
punctuation character, then the maximum value is 1; if the result was
@@ -14682,11 +14689,11 @@
<dt>The actual value
<dd>
- <p>If the <code title=attr-meter-value><a href="#value3">value</a></code>
+ <p>If the <code title=attr-meter-value><a href="#value4">value</a></code>
attribute is specified and a value could be parsed out of it, then that
value is the actual value.</p>
- <p>If the <code title=attr-meter-value><a href="#value3">value</a></code>
+ <p>If the <code title=attr-meter-value><a href="#value4">value</a></code>
attribute is not specified but the <code title=attr-meter-max><a
href="#max1">max</a></code> attribute <em>is</em> specified and the
result of processing the <code><a
@@ -14695,7 +14702,7 @@
is the actual value.</p>
<p>If neither of the <code title=attr-meter-value><a
- href="#value3">value</a></code> and <code title=attr-meter-max><a
+ href="#value4">value</a></code> and <code title=attr-meter-max><a
href="#max1">max</a></code> attributes are specified, then, if the
result of processing the <code><a
href="#textcontent">textContent</a></code> of the element was one number
@@ -14832,7 +14839,7 @@
</div>
<p>The <dfn id=min0 title=dom-meter-min><code>min</code></dfn>, <dfn
- id=max2 title=dom-meter-max><code>max</code></dfn>, <dfn id=value4
+ id=max2 title=dom-meter-max><code>max</code></dfn>, <dfn id=value5
title=dom-meter-value><code>value</code></dfn>, <dfn id=low0
title=dom-meter-low><code>low</code></dfn>, <dfn id=high0
title=dom-meter-high><code>high</code></dfn>, and <dfn id=optimum0
@@ -14843,7 +14850,7 @@
href="#textcontent">textContent</a></code> never affects the DOM values.
<p class=big-issue>Would be cool to have the <code title=dom-meter-value><a
- href="#value4">value</a></code> DOM attribute update the <code><a
+ href="#value5">value</a></code> DOM attribute update the <code><a
href="#textcontent">textContent</a></code> in-line...</p>
<!-- XXX
should we also look inside the title="" attribute?
@@ -18345,7 +18352,7 @@
<dd><code title=attr-param-name><a href="#name5">name</a></code>
- <dd><code title=attr-param-value><a href="#value5">value</a></code>
+ <dd><code title=attr-param-value><a href="#value6">value</a></code>
<dt>DOM interface:
@@ -18353,7 +18360,7 @@
<pre
class=idl>interface <dfn id=htmlparamelement>HTMLParamElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
attribute DOMString <a href="#name6" title=dom-param-name>name</a>;
- attribute DOMString <a href="#value6" title=dom-param-value>value</a>;
+ attribute DOMString <a href="#value7" title=dom-param-value>value</a>;
};</pre>
</dl>
@@ -18363,7 +18370,7 @@
<p>The <dfn id=name5 title=attr-param-name><code>name</code></dfn>
attribute gives the name of the parameter.
- <p>The <dfn id=value5 title=attr-param-value><code>value</code></dfn>
+ <p>The <dfn id=value6 title=attr-param-value><code>value</code></dfn>
attribute gives the value of the parameter.
<p>Both attributes must be present. They may have any value.
@@ -18375,7 +18382,7 @@
name/value pair.
<p>The DOM attributes <dfn id=name6
- title=dom-param-name><code>name</code></dfn> and <dfn id=value6
+ title=dom-param-name><code>name</code></dfn> and <dfn id=value7
title=dom-param-value><code>value</code></dfn> must both <a
href="#reflect">reflect</a> the respective content attributes of the same
name.
@@ -27112,7 +27119,7 @@
<dd><code title=attr-input-type><a href="#type12">type</a></code>
- <dd><code title=attr-input-value><a href="#value7">value</a></code>
+ <dd><code title=attr-input-value><a href="#value8">value</a></code>
<dt>DOM interface:
@@ -27145,7 +27152,7 @@
attribute DOMString <a href="#target4" title=dom-fs-target>target</a>;
attribute DOMString <a href="#type13" title=dom-input-type>type</a>;
attribute DOMString <a href="#defaultvalue" title=dom-input-defaultValue>defaultValue</a>;
- attribute DOMString <a href="#value8" title=dom-input-value>value</a>;
+ attribute DOMString <a href="#value9" title=dom-input-value>value</a>;
attribute DOMTimeStamp <a href="#valueasdate" title=dom-input-valueAsDate>valueAsDate</a>;
attribute float <a href="#valueasnumber" title=dom-input-valueAsNumber>valueAsNumber</a>;
readonly attribute <a href="#htmloptionelement">HTMLOptionElement</a> <a href="#selectedoption" title=dom-input-selectedOption>selectedOption</a>;
@@ -28606,8 +28613,8 @@
state must be invoked.
<p>Each <code><a href="#input0">input</a></code> element has a <a
- href="#value10" title=concept-fe-value>value</a>, which is exposed by the
- <code title=dom-input-value><a href="#value8">value</a></code> DOM
+ href="#value11" title=concept-fe-value>value</a>, which is exposed by the
+ <code title=dom-input-value><a href="#value9">value</a></code> DOM
attribute.
<p>Each <code><a href="#input0">input</a></code> element has a boolean <dfn
@@ -28637,13 +28644,13 @@
href="#dirty0">dirty</a></i>) when the element is created, and must be set
to true (<i title=concept-input-dirty><a href="#dirty0">dirty</a></i>)
whenever the user interacts with the control in a way that changes the <a
- href="#value10" title=concept-fe-value>value</a>.
+ href="#value11" title=concept-fe-value>value</a>.
- <p>The <dfn id=value7 title=attr-input-value><code>value</code></dfn>
- content attribute gives the default <a href="#value10"
+ <p>The <dfn id=value8 title=attr-input-value><code>value</code></dfn>
+ content attribute gives the default <a href="#value11"
title=concept-fe-value>value</a> of the <code><a
href="#input0">input</a></code> element. When the <code
- title=attr-input-value><a href="#value7">value</a></code> content
+ title=attr-input-value><a href="#value8">value</a></code> content
attribute is added, set, or removed, and when the element is first
created, after invoking the <a href="#control0">control initialization
algorithm</a>, the <dfn id=default2>default value change algorithm</dfn>
@@ -28698,7 +28705,7 @@
id=defaultvalue
title=dom-input-defaultValue><code>defaultValue</code></dfn> DOM attribute
must <a href="#reflect">reflect</a> the <code title=attr-input-value><a
- href="#value7">value</a></code> content attribute.
+ href="#value8">value</a></code> content attribute.
<p>The <code title=dom-cva-willValidate><a
href="#willvalidate">willValidate</a></code>, <code
@@ -28737,18 +28744,18 @@
<a href="#default2">default value change algorithm</a> is as
follows:</strong> If the <code><a href="#input0">input</a></code> element
is not <i title=concept-input-dirty><a href="#dirty0">dirty</a></i> then
- set the <a href="#value10" title=concept-fe-value>value</a> of the element
+ set the <a href="#value11" title=concept-fe-value>value</a> of the element
to the value of the <code title=attr-input-value><a
- href="#value7">value</a></code> content attribute and <a
+ href="#value8">value</a></code> content attribute and <a
href="#strip">strip line breaks from the value</a>.
<p>If an <code><a href="#input0">input</a></code> element whose <code
title=attr-input-type><a href="#type12">type</a></code> attribute is in
the <a href="#text2" title=attr-input-type-text>Text</a> state is <i
title=concept-input-mutable><a href="#mutable">mutable</a></i>, its <a
- href="#value10" title=concept-fe-value>value</a> should be editable by the
+ href="#value11" title=concept-fe-value>value</a> should be editable by the
user. User agents must not allow users to insert U+000A LINE FEED (LF) or
- U+000D CARRIAGE RETURN (CR) characters into the <a href="#value10"
+ U+000D CARRIAGE RETURN (CR) characters into the <a href="#value11"
title=concept-fe-value>value</a> of such <code><a
href="#input0">input</a></code> elements.
@@ -29013,7 +29020,7 @@
<p>When a user agent is to <dfn id=strip>strip line breaks from the
value</dfn>, the user agent must remove any U+000A LINE FEED (LF) and
- U+000D CARRIAGE RETURN (CR) characters from <a href="#value10"
+ U+000D CARRIAGE RETURN (CR) characters from <a href="#value11"
title=concept-fe-value>value</a>.
<h5 id=common4><span class=secno>4.9.4.2. </span>Common <code><a
@@ -29091,17 +29098,66 @@
<h5 id=common5><span class=secno>4.9.4.3. </span>Common <code><a
href="#input0">input</a></code> element APIs</h5>
- <p class=big-issue>... <dfn id=checked1
- title=dom-input-checked><code>checked</code></dfn>
+ <h6 id=value><span class=secno>4.9.4.3.1. </span>Value manipulation</h6>
- <p class=big-issue>... <dfn id=value8
+ <p class=big-issue>... <dfn id=value9
title=dom-input-value><code>value</code></dfn>
- <p class=big-issue>... <dfn id=valueasdate
- title=dom-input-valueAsDate><code>valueAsDate</code></dfn>
+ <hr>
- <p class=big-issue>... <dfn id=valueasnumber
- title=dom-input-valueAsNumber><code>valueAsNumber</code></dfn>
+ <p>The <dfn id=valueasdate
+ title=dom-input-valueAsDate><code>valueAsDate</code></dfn> DOM attribute
+ represents the <span title=concept-input-value>value</span> of the
+ element, interpreted as a date.
+
+ <p>On getting, if the <code title=dom-input-valueAsDate><a
+ href="#valueasdate">valueAsDate</a></code> attribute applies, as defined
+ for the <code><a href="#input0">input</a></code> element's <code
+ title=attr-input-type><a href="#type12">type</a></code> attribute's
+ current state, then run the <dfn id=valueasdate0><code
+ title=dom-input-valueAsDate>valueAsDate</code> getter algorithm</dfn>
+ defined for that state. Otherwise, return a Not-a-Number (NaN) value.
+
+ <p>On setting, if the <code title=dom-input-valueAsDate><a
+ href="#valueasdate">valueAsDate</a></code> attribute applies, as defined
+ for the <code><a href="#input0">input</a></code> element's <code
+ title=attr-input-type><a href="#type12">type</a></code> attribute's
+ current state, then run the <dfn id=valueasdate1><code
+ title=dom-input-valueAsDate>valueAsDate</code> setter algorithm</dfn>
+ defined for that state. Otherwise, do nothing.
+
+ <hr>
+
+ <p>The <dfn id=valueasnumber
+ title=dom-input-valueAsNumber><code>valueAsNumber</code></dfn> DOM
+ attribute represents the <span title=concept-input-value>value</span> of
+ the element, interpreted as a number.
+
+ <p>On getting, if the <code title=dom-input-valueAsNumber><a
+ href="#valueasnumber">valueAsNumber</a></code> attribute applies, as
+ defined for the <code><a href="#input0">input</a></code> element's <code
+ title=attr-input-type><a href="#type12">type</a></code> attribute's
+ current state, then run the <dfn id=valueasnumber0><code
+ title=dom-input-valueAsNumber>valueAsNumber</code> getter algorithm</dfn>
+ defined for that state. Otherwise, return the <span
+ title=concept-input-value>value</span> of the element, cast to the type of
+ the DOM attribute.
+
+ <p>On setting, if the <code title=dom-input-valueAsNumber><a
+ href="#valueasnumber">valueAsNumber</a></code> attribute applies, as
+ defined for the <code><a href="#input0">input</a></code> element's <code
+ title=attr-input-type><a href="#type12">type</a></code> attribute's
+ current state, then run the <dfn id=valueasnumber1><code
+ title=dom-input-valueAsNumber>valueAsNumber</code> setter algorithm</dfn>
+ defined for that state. Otherwise, the <span
+ title=concept-input-value>value</span> must be set to the shortest
+ possible representation of the given value that is a <a
+ href="#valid1">valid floating point number</a> in base ten.
+
+ <h6 id=others...><span class=secno>4.9.4.3.2. </span>Others...</h6>
+
+ <p class=big-issue>... <dfn id=checked1
+ title=dom-input-checked><code>checked</code></dfn>
<p class=big-issue>... <dfn id=list
title=dom-input-list><code>list</code></dfn>
@@ -29414,7 +29470,7 @@
attribute DOMString <span title=dom-option-label>label</span>;
attribute boolean <span title=dom-option-defaultSelected>defaultSelected</span>;
attribute boolean <span title=dom-option-selected>selected</span>;
- attribute DOMString <a href="#value8" title=dom-input-value>value</a>;
+ attribute DOMString <a href="#value9" title=dom-input-value>value</a>;
readonly attribute DOMString <span title=dom-option-text>text</span>;
readonly attribute long <span title=dom-option-index>index</span>;
@@ -29426,7 +29482,7 @@
<p class=big-issue>... <dfn id=selected1
title=concept-option-selected>selected</dfn>
- <p class=big-issue>... <dfn id=value9
+ <p class=big-issue>... <dfn id=value10
title=concept-option-value>value</dfn>
<p class=big-issue> <dfn id=option0
@@ -29735,7 +29791,7 @@
<p class=big-issue>... <dfn id=disabled6
title=dom-fe-disabled>disabled</dfn> DOM attribute
- <p class=big-issue>... <dfn id=value10 title=concept-fe-value>value</dfn></p>
+ <p class=big-issue>... <dfn id=value11 title=concept-fe-value>value</dfn></p>
<!-- XXX autocomplete: define somewhere that the value may be set from a stored value -->
<h4 id=attributes2><span class=secno>4.9.14 </span><dfn
@@ -30082,7 +30138,7 @@
href="#select">select</a></code> element that is <a href="#selected1"
title=concept-option-selected>selected</a>, append an entry in the
<var title="">form data set</var> with the <var title="">name</var> as
- the name and the <a href="#value9"
+ the name and the <a href="#value10"
title=concept-option-value>value</a> of the <code><a
href="#option">option</a></code> element as the value.
@@ -30100,7 +30156,7 @@
<li>
<p>Otherwise, append an entry in the <var title="">form data set</var>
- with <var title="">name</var> as the name and the <a href="#value10"
+ with <var title="">name</var> as the name and the <a href="#value11"
title=concept-fe-value>value</a> of the <var title="">field</var>
element as the value.
</ol>
@@ -32812,7 +32868,7 @@
<p>The <code title=dom-provider-getCellData><a
href="#getcelldata">getCellData()</a></code> method must return the
- <code title=dom-input-value><a href="#value8">value</a></code> of the
+ <code title=dom-input-value><a href="#value9">value</a></code> of the
<code><a href="#input0">input</a></code> element.</p>
<p>The <code title=dom-provider-getCellClasses><a
@@ -32823,7 +32879,7 @@
<p>The <code title=dom-provider-editCell><a
href="#editcell">editCell()</a></code> method must set the <code><a
href="#input0">input</a></code> element's <code title=dom-input-value><a
- href="#value8">value</a></code> DOM attribute to the value of the third
+ href="#value9">value</a></code> DOM attribute to the value of the third
argument to the method.</p>
<p>The <code title=dom-provider-setCellCheckedState><a
@@ -34707,7 +34763,7 @@
<p>If the <a href="#type22" title=command-facet-Type>Type</a> is "command",
then it is the string given by the <code title=attr-input-value><a
- href="#value7">value</a></code> attribute, if any, and a
+ href="#value8">value</a></code> attribute, if any, and a
<span>UA-dependent value</span><!-- XXX xref--> that the UA uses to label
the button itself if the attribute is absent.
@@ -34719,7 +34775,7 @@
question is the <a href="#label4" title=command-facet-Label>Label</a> (in
DOM terms, this the string given by <code><var
title="">element</var>.labels[0].textContent</code>). Otherwise, the value
- of the <code title=attr-input-value><a href="#value7">value</a></code>
+ of the <code title=attr-input-value><a href="#value8">value</a></code>
attribute, if present, is the <a href="#label4"
title=command-facet-Label>Label</a>. Otherwise, the <a href="#label4"
title=command-facet-Label>Label</a> is the empty string.
@@ -45197,7 +45253,7 @@
default value. For <code><a href="#input0">input</a></code> elements
this means updating the <code title=dom-input-defaultValue><a
href="#defaultvalue">defaultValue</a></code> DOM attribute as well as
- the <code title=dom-input-value><a href="#value8">value</a></code> DOM
+ the <code title=dom-input-value><a href="#value9">value</a></code> DOM
attribute; for <code><a href="#select">select</a></code> elements it
means updating the <code><a href="#option">option</a></code> elements'
<code title=dom-option-defaultSelected>defaultSelected</code> DOM
@@ -49738,7 +49794,7 @@
<div class=example>
<p>In the following example, the <code title=attr-input-value><a
- href="#value7">value</a></code> attribute is given with the unquoted
+ href="#value8">value</a></code> attribute is given with the unquoted
attribute value syntax:</p>
<pre><input <em>value=yes</em>></pre>
Received on Thursday, 18 September 2008 00:46:42 UTC